Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macos-13 pipeline failure on codecov-action #839

Closed
viirya opened this issue Aug 17, 2024 · 0 comments · Fixed by #933
Closed

macos-13 pipeline failure on codecov-action #839

viirya opened this issue Aug 17, 2024 · 0 comments · Fixed by #933
Labels
bug Something isn't working

Comments

@viirya
Copy link
Member

viirya commented Aug 17, 2024

Describe the bug

macos-13/java 17-spark-4.0/java

Run codecov/codecov-action@v3
  with:
  env:
    RUST_VERSION: stable
    DYLD_LIBRARY_PATH: /usr/local/opt/openssl@3/lib:
    JAVA_HOME: /Users/runner/hostedtoolcache/Java_Zulu_jdk/17.0.12-7/x64
    JAVA_HOME_17_X64: /Users/runner/hostedtoolcache/Java_Zulu_jdk/17.0.12-7/x64
==> macos OS detected
https://uploader.codecov.io/latest/macos/codecov.SHA256SUM
==> SHASUM file signed by key id 806bb28aed779869
==> Uploader SHASUM verified (75086ee436f6f74c4e8f65448eaa399e38bc93bb27a53d057b24b275b9f78c89  codecov)
==> Running version latest
==> Running version v0.8.0
/Users/runner/work/_actions/codecov/codecov-action/v3/dist/codecov -n  -Q github-action-3.1.6
Error: spawn Unknown system error -86
    at ChildProcess.spawn (node:internal/child_process:421:11)
    at Object.spawn (node:child_process:761:9)
    at ToolRunner.<anonymous> (/Users/runner/work/_actions/codecov/codecov-action/v3/webpack:/codecov-action/node_modules/@actions/exec/lib/toolrunner.js:413:1)

Opened codecov/codecov-action#1549 for getting more info.

Steps to reproduce

No response

Expected behavior

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant