diff options
| author | Pierrick Bouvier <101587250+pbo-linaro@users.noreply.github.com> | 2022-10-20 11:06:09 +0200 |
|---|---|---|
| committer | Richard Lau <rlau@redhat.com> | 2022-12-07 09:07:17 -0500 |
| commit | 821d832cef66e8ce274679bbcaa8a516db3230ef (patch) | |
| tree | abb7f1ac602b7dc80a39e881ac19a437f791a739 | |
| parent | 96d131665ed4ab6604ccfc92eb75350f1ab4ab62 (diff) | |
| download | node-new-821d832cef66e8ce274679bbcaa8a516db3230ef.tar.gz | |
test: mark test-watch-mode* as flaky on all platforms
This was confirmed flaky on those platforms:
- Windows x64
- Windows on Arm
- Linux
- Freebsd
Tests randomly fail because of bad order in messages expected, which
seems related to threads scheduling at execution.
PR-URL: https://github.com/nodejs/node/pull/45049
Backport-PR-URL: https://github.com/nodejs/node/pull/44873
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
| -rw-r--r-- | test/sequential/sequential.status | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/test/sequential/sequential.status b/test/sequential/sequential.status index 56f9667d7a..5d88747b70 100644 --- a/test/sequential/sequential.status +++ b/test/sequential/sequential.status @@ -7,6 +7,9 @@ prefix sequential [true] # This section applies to all platforms # https://github.com/nodejs/node/issues/27611#issuecomment-613100468 test-cpu-prof-dir-worker: PASS, FLAKY +# https://github.com/nodejs/node/issues/44898 +test-watch-mode: PASS, FLAKY +test-watch-mode-inspect: PASS, FLAKY [$system==win32] |