-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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: mark test-fs-readdir-ucs2 flaky #13989
test: mark test-fs-readdir-ucs2 flaky #13989
Conversation
+1 for fast-tracking |
CI: https://ci.nodejs.org/view/All/job/node-test-pull-request/8875/ Landed in 47d1e12, fast tracked. |
PR-URL: #13989 Reviewed-By: Refael Ackermann <[email protected]>
Just to see it pass (well, yellow) CI on |
Isn't that for Alpine? This is unrelated, the CI will remain yellow, which makes sense to me since |
Yes, right. 🤦♂️ |
PR-URL: #13989 Reviewed-By: Refael Ackermann <[email protected]>
PR-URL: #13989 Reviewed-By: Refael Ackermann <[email protected]>
PR-URL: #13989 Reviewed-By: Refael Ackermann <[email protected]>
PR-URL: #13989 Reviewed-By: Refael Ackermann <[email protected]>
PR-URL: #13989 Reviewed-By: Refael Ackermann <[email protected]>
Changes in our CI infra makes
test-fs-readdir-ucs2
fail every run on Raspberry Pi (ref: nodejs/build#774 (comment)).While we need to find a better solution, I suggest we mark the test as flaky to avoid having every run red because of this.
@nodejs/testing @nodejs/ctc any objection for fast tracking?
Ref: nodejs/build#774
Ref: #13986
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
Test