-
Notifications
You must be signed in to change notification settings - Fork 224
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] Unexpected working directory since recent update #1767
Comments
I suspect that this is not the actual issue but rather a symlink issue: The uploader later runs I did that manually:
Output:
So the git commands all fail because the I found this in the output of the checkout action:
So that does the right thing but only in a temporary folder. Edit: Not a necessarily a symlink issue: The job runs in a container, which is a change on our side as before we didn't use a container. |
@Flamefire oh this is fascinating, there is an option to turn off safe directory setting in the Action with |
I'll try but I don't see how. I mean this just does not add the (wrong) directory so the "right" one will still be missing causing the error. I think a solution is to use Line 184 in 4898080
I did a quick check:
Edit: |
Describe the bug
(I think) since one of the updates at/on v4/v5 the default working directory of the action is changed.
Previously it seemed to always run in
$GITHUB_WORKSPACE
but now it uses whatever folder is set by the previous step.This is a problem because the relevant source files will not be found, especially due to a bug in the CLI tool and hence the path fixup are not done and the coverage report will be wrong, e.g. showing many new files that cannot be associated with files in the repo
To Reproduce
Steps to reproduce the behavior:
/__w/
Expected behavior
Default
working-directory
should likely be$GITHUB_WORKSPACE
such that the report is correct.Regression
Not exactly sure which version did work or if this was a change from GitHub actions triggering this
Product Area
Coverage
Versions
Commit and CI link
CI run
The text was updated successfully, but these errors were encountered: