411f3e03feI haven't seen test-npm-install fail on arm in a long time. There is no open issue for it being unreliable. Remove flaky designation in parallel.status file. (If it turns out it is flaky, it's easy enough to open an issue and restore the flaky designation.) Ref: https://github.com/nodejs/node/issues/13498 PR-URL: https://github.com/nodejs/node/pull/19216 Refs: https://github.com/nodejs/node/issues/13498 Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
23 lines
530 B
Text
23 lines
530 B
Text
prefix parallel
|
|
|
|
# To mark a test as flaky, list the test name in the appropriate section
|
|
# below, without ".js", followed by ": PASS,FLAKY". Example:
|
|
# sample-test : PASS,FLAKY
|
|
|
|
[true] # This section applies to all platforms
|
|
# Postmortem debugging data is prone to accidental removal during V8 updates.
|
|
test-postmortem-metadata: PASS,FLAKY
|
|
|
|
[$system==win32]
|
|
|
|
[$system==linux]
|
|
|
|
[$system==macos]
|
|
|
|
[$arch==arm || $arch==arm64]
|
|
|
|
[$system==solaris] # Also applies to SmartOS
|
|
|
|
[$system==freebsd]
|
|
|
|
[$system==aix]
|