test: mark test-fs-readdir-ucs2 flaky

[joaocgreis]

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), or vcbuild test (Windows) passes
• commit message follows commit guidelines

Affected core subsystem(s)

Test

[refack]

+1 for fast-tracking

[joaocgreis]

CI: https://ci.nodejs.org/view/All/job/node-test-pull-request/8875/

Landed in 47d1e12, fast tracked.

[refack]

Just to see it pass (well, yellow) CI on master: https://ci.nodejs.org/job/node-test-commit/10826/
#13985 will turn in green again 🙏

[joaocgreis]

#13985 will turn in green again 🙏

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.

[refack]

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.

Yes, right. 🤦‍♂️