-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
tap2junit/build/python nightly failed with unicode problem #31225
Comments
FWIW the failing test is #31094 and has also been observed failing on freebsd, https://ci.nodejs.org/job/node-test-commit-freebsd/30729/nodes=freebsd11-x64/console where it also caused the tap2junit failure reported in this issue. |
Looked at last four failed jobs. https://ci.nodejs.org/job/node-daily-master/1932/ It seems that the unicode related error is no longer causes problem. pummel/test-net-throttle fails in the jobs I mentioned earlier. It's written in the README that pummel directory doesn't run on CI. Unfortunately, I can't see the last success job and don't have access to CI configuration. Could anyone tell if tests in this job should pass with no errors? I tried to launch the same command that CI does. There were 25 errors. |
@richardlau @sam-github Could anyone please answer my question above? I made a couple of pull requests during the last two month. Every second job that were launched through my PRs failed because of flaky tests or other not related to my code reasons. Therefore, I think that this issue is very important. Daily builds allow us to monitor stability of master branch. Ready to help here, but I don't have access to CI configuration because I'm not a colloborator. I checked the last two failed jobs. Just to make sure that the builds still fail. https://ci.nodejs.org/job/node-test-commit-linux/nodes=alpine-latest-x64/35728/
https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/14966
|
I think there is a Unicode issue with tap2junit but it only manifests if a test fails that happens to output certain Unicode characters. Otherwise yes unfortunately we do have flaky tests and not many people appear to be monitoring the daily builds on a regular basis. There is an OpenJS World Collaborator Summit session on CI Stability this Thursday for folks to get together to brainstorm ideas. |
I'm looking at this job. @richardlau please correct me if i'm wrong. |
Correct, you're not seeing the Unicode issue. https://ci.nodejs.org/job/node-test-commit-linux/35719/nodes=alpine-latest-x64/console is probably related to the alpine changes in nodejs/build#2364 (cc @rvagg) |
the alpine problem should be gone now with nodejs/build#2364 merged - it's excluded from 10 and 12.x now |
Nightly build from 2 days ago:
OS failure:
The text was updated successfully, but these errors were encountered: