-
Notifications
You must be signed in to change notification settings - Fork 167
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
test/arm reported as failure when it passed for a PR #572
Comments
Hmm, this is still happening, nodejs/node#10517 (https://ci.nodejs.org/job/node-test-commit/6915/) for a CI run that's still in Jenkins. |
Can confirm. The jenkins script for notifying is likely to blame and I've looked at it a few times; can't quite figure it out. Still on it. |
Should be fixed. It was running the two scripts (for success and failure) unconditionally, so it would mark it as success and immediately mark it as failure. I tested with a success, I don't have a PR that fails to test. |
AIX was reporting success when the job fails, so I changed it as well but did not test (cc @mhdawson) |
To test on AIX is what we we need a PR that fails on AIX, and we run the CI job with the results posted to the PR and we then validate that it shows as failed ? |
@gibfahn thanks! |
Examples:
The text was updated successfully, but these errors were encountered: