Commit 4f858d2
test: skip test-fs-cp* tests that are constantly failing on Windows
These tests are likely actual regressions introduced when the
monolithic test-fs-cp.mjs was marked as flaky and got ignored due
to the flaky status. They are now constantly failing the Windows
CI and require the CI to always be re-run on Windows when the job
is resumed. Simply skip them until someone fixes them, as there's
no point keep running these known regressions on Windows anymore.
PR-URL: #59637
Refs: #59636
Refs: #59408
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Stefan Stojanovic <stefan.stojanovic@janeasystems.com>1 parent 8a504d9 commit 4f858d2
1 file changed
Lines changed: 5 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -27,6 +27,11 @@ test-sqlite: PASS, FLAKY | |||
| 27 | 27 | test-runner-watch-mode-complex: PASS, FLAKY | |
| 28 | 28 | # https://github.com/nodejs/node/issues/54808 | |
| 29 | 29 | test-async-context-frame: PASS, FLAKY | |
| 30 | + # https://github.com/nodejs/node/issues/59636 | ||
| 31 | + test-fs-cp-sync-error-on-exist: SKIP | ||
| 32 | + test-fs-cp-sync-symlink-points-to-dest-error: SKIP | ||
| 33 | + test-fs-cp-async-symlink-points-to-dest: SKIP | ||
| 34 | + test-fs-cp-sync-unicode-folder-names: SKIP | ||
| 30 | 35 | ||
| 31 | 36 | # https://github.com/nodejs/node/issues/56751 | |
| 32 | 37 | test-without-async-context-frame: PASS, FLAKY | |
0 commit comments