You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error is triggered when some of my unit-test fails. My understanding is that I should have a nice-ish report and not a bash error ?
The error indicates that the file CodeCoverage does not exist. The last line of dist/platforms/ubuntu/run_tests.sh does make a call to chmod without checking for file presence. Maybe wrapping it with a check would help ?
I checked the various paramaters for code coverage to see if I could disable the feature, but as far as I know, the file name CodeCoverage is hardcoded in the action and the chmod cannot be avoided via configuration.
See the following places for the hardcoded string :
main.ts:71
image-environment-factory.ts:37
Is there a way to avoid the failure of the CI ?
The text was updated successfully, but these errors were encountered:
I fixed this by installing the Code Coverage tool in my unity project, the error does not seem to show that this might be the issue, but once I installed that package to the project it instantly worked!
Bug description
After running the unit-test action for edit mode tests with the following error :
How to reproduce
Trigger the unit test ci.
Not sure.
Additional details
The error is triggered when some of my unit-test fails. My understanding is that I should have a nice-ish report and not a bash error ?
The error indicates that the file
CodeCoverage
does not exist. The last line ofdist/platforms/ubuntu/run_tests.sh
does make a call tochmod
without checking for file presence. Maybe wrapping it with a check would help ?I checked the various paramaters for code coverage to see if I could disable the feature, but as far as I know, the file name
CodeCoverage
is hardcoded in the action and the chmod cannot be avoided via configuration.See the following places for the hardcoded string :
main.ts:71
image-environment-factory.ts:37
Is there a way to avoid the failure of the CI ?
The text was updated successfully, but these errors were encountered: