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

BUG: Test-runner actions fails with a "chmod: cannot access '/github/workspace/CodeCoverage': No such file or directory" error #218

Open
SimonDarksideJ opened this issue Mar 30, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@SimonDarksideJ
Copy link

Bug description

Test-runner actions fails with a "chmod: cannot access '/github/workspace/CodeCoverage': No such file or directory" error.

*Note, there were no actual tests in the project but this should not prevent the action from completing successfully.

How to reproduce

Visit public repo and examine setup, replicate for test:
https://github.com/SimonDarksideJ/TheMostAwesomeGameEverMade/actions/runs/4566129759

  • Expected behavior

The action should complete successfully?

Additional details

Output from end of log

Run succeeded, no failures occurred

###########################
#    COMBINE_RESULTS Results    #
###########################

chmod: cannot access '/github/workspace/CodeCoverage': No such file or directory
Changing to "/github/workspace/_activate-license" directory.
/github/workspace/_activate-license /github/workspace
/github/workspace

###########################
#         Failure         #
###########################

Please note that the exit code is not very descriptive.
Most likely it will not help you solve the issue.

To find the reason for failure: please search for errors in the log above.

Error: The process '/usr/bin/docker' failed with exit code 139
@SimonDarksideJ SimonDarksideJ added the bug Something isn't working label Mar 30, 2023
@SmailikHappy
Copy link

Ping pong. Is there any update on this issue? I am facing with the same error as well.

@webbertakken
Copy link
Member

Recommended workaround: add tests to your project.

We're happy to take PRs that fix the chmod task, so that it only runs if the folder exists.

@QuakeEye
Copy link
Contributor

Next to adding tests, also make sure the Code Coverage package is added to your unity project! That missing was what was causing the error for me.

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

No branches or pull requests

4 participants