-
Notifications
You must be signed in to change notification settings - Fork 166
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
Immediate failures on smartos, linux-containered, arm, and linuxone #1467
Comments
I'm not sure what caused it, but @joyeecheung left comments on a bunch of PRs last night saying to rebase the PR to make that go away. It worked for me. |
The cause is a combination of old git versions and a bad commit (that was fixed nodejs/node#22340): |
Thanks! I've rebased and will start a new CI. |
Oh, I guess the REBASE_ONTO wasn't working because the repo wasn't clean. |
Hmmm ... why does the linuxone sub-job list a whole pile of changes? |
It's not an amazing feature. It compares the code to the last state of the workspace. |
Closing as it this appears to have been resolved. Please re-open if the problem persists |
https://ci.nodejs.org/job/node-test-pull-request/16595/
https://ci.nodejs.org/job/node-test-pull-request/16597/
https://ci.nodejs.org/job/node-test-pull-request/16602/
https://ci.nodejs.org/job/node-test-pull-request/16603/
On all of them, the above-mentioned platforms fail with "You have unstaged changes".
The text was updated successfully, but these errors were encountered: