When setting runAsHostUser to true, the action gets the host user/group information using the stat -c command on "$fullProjectPath", however, this fullProjectPath variable is never set. This results in the following error message:
stat: cannot statx '': No such file or directory
Error: The process '/usr/bin/docker' failed with exit code 1
and then the action aborts.
How to reproduce
Start the unity-test-runner action on a self-hosted runner (running Ubuntu) with runAsHostUser set to true.
Expected behavior
I expect the action to run as host user (the full project path would need to be set) and not abort.
Additional details
The problem might also be a configuration problem on my side, but I believe the problem is in the entrypoint.sh file, above line 16. I think the line where the fullProjectPath is being set is missing. (or at least I compared to the entrypoint.sh of unity-builder, and there at line 14 the fullProjectPath variable is set, so I think this line is needed for the unity-test-runner as well.
fullProjectPath="$GITHUB_WORKSPACE/$PROJECT_PATH"
I hope I described the issue sufficiently, if not I'd be happy to provide more details. Thank you for your help!
Bug description
When setting
runAsHostUser
to true, the action gets the host user/group information using thestat -c
command on"$fullProjectPath"
, however, this fullProjectPath variable is never set. This results in the following error message:and then the action aborts.
How to reproduce
Start the unity-test-runner action on a self-hosted runner (running Ubuntu) with
runAsHostUser
set to true.Expected behavior
I expect the action to run as host user (the full project path would need to be set) and not abort.
Additional details
The problem might also be a configuration problem on my side, but I believe the problem is in the entrypoint.sh file, above line 16. I think the line where the fullProjectPath is being set is missing. (or at least I compared to the entrypoint.sh of unity-builder, and there at line 14 the fullProjectPath variable is set, so I think this line is needed for the unity-test-runner as well.
I hope I described the issue sufficiently, if not I'd be happy to provide more details. Thank you for your help!