| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
+1 for fast-tracking |
Sorry, something went wrong.
|
CI: https://ci.nodejs.org/view/All/job/node-test-pull-request/8875/ Landed in 47d1e12, fast tracked. |
Sorry, something went wrong.
PR-URL: #13989 Reviewed-By: Refael Ackermann <refack@gmail.com>
|
Just to see it pass (well, yellow) CI on master: https://ci.nodejs.org/job/node-test-commit/10826/ |
Sorry, something went wrong.
Isn't that for Alpine? This is unrelated, the CI will remain yellow, which makes sense to me since test-fs-readdir-ucs2 is a valid test and we're not getting results to it from the Pis. |
Sorry, something went wrong.
Yes, right. 🤦♂️ |
Sorry, something went wrong.
PR-URL: #13989 Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: #13989 Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: #13989 Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: #13989 Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: #13989 Reviewed-By: Refael Ackermann <refack@gmail.com>
| Back | FazBrowse Home | New Git URL |
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
Affected core subsystem(s)
Test