-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
test: mark test-inspector-network-fetch as flaky on Windows #59091
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
test: mark test-inspector-network-fetch as flaky on Windows #59091
Conversation
Fast-track has been requested by @joyeecheung. Please 👍 to approve. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #59091 +/- ##
==========================================
- Coverage 90.06% 90.05% -0.02%
==========================================
Files 645 645
Lines 189130 189153 +23
Branches 37094 37097 +3
==========================================
Hits 170339 170339
- Misses 11511 11515 +4
- Partials 7280 7299 +19 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the change!
I'm currently investigating it.
Landed in b16a0e7 |
The first failure happened in #58077 which is likely related. @islandryu is investigating but meanwhile IMO it would be better to mark it as flaky to unblock the CI since this has failed a lot of Windows CIs since the security embargo is lifted. (https://ci.nodejs.org/job/node-test-binary-windows-js-suites/ is almost all red)
Refs: #59090