-
-
Notifications
You must be signed in to change notification settings - Fork 32.9k
test: skip test-fs-cp* tests that are constantly failing on Windows #59637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
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.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #59637 +/- ##
==========================================
- Coverage 89.85% 89.83% -0.02%
==========================================
Files 667 667
Lines 196260 196488 +228
Branches 38559 38588 +29
==========================================
+ Hits 176341 176521 +180
- Misses 12368 12423 +55
+ Partials 7551 7544 -7 🚀 New features to boost your workflow:
|
|
Can they potentially be moved to |
|
I don't know how to make the known-issues machinery support platform-specific marking, unless you know how to make it only expect failures on Windows but not on other platforms? |
|
Landed in 2822585 |


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.
Refs: #59636
Refs: #59408