-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
[v20.x] test: skip test-buffer-tostring-range on smartos #56727
Conversation
test-buffer-tostring-range
as flaky
Please remove Fixes: from the issue description, otherwise the tracking issue will be closed when this lands. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #56727 +/- ##
=======================================
Coverage 89.21% 89.21%
=======================================
Files 662 662
Lines 191945 191945
Branches 36948 36945 -3
=======================================
+ Hits 171238 171246 +8
+ Misses 13549 13541 -8
Partials 7158 7158 |
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.
Should this land on other release lines than 20.x? Looking at daily, it's failing only on 20.x
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.
I think on v20.x it's not flaky, it's just 100% failure...so if you plan to backport it to v20.x it might be better to just use SKIP
there.
Actually, no, this is not flaky on the main branch, it's only 100% failure on v20.x. See https://github.com/nodejs/reliability/blob/main/reports/2025-01-23.md - both PRs referenced are targetting v20.x |
I'm move this to v20.x only |
2588b7d
to
fd49394
Compare
fd49394
to
a7bc6cc
Compare
test-buffer-tostring-range
as flakytest-buffer-tostring-range
as flaky
a7bc6cc
to
cc3ca7a
Compare
416c658
to
cc7d1a7
Compare
315bb71
to
f4ac0e1
Compare
The branch (v20.x-staging) seems to fail consistently on windows for permission model @RafaelGSS
|
@marco-ippolito I'll fix it Monday. Sorry about it. |
maybe its just flaky nodejs/reliability#1096, but It seems very hard to get a green ci 😭 |
f487855
to
b5d87d0
Compare
Ci is extremely flaky 😭😭😭😭 |
@nodejs/build osx is constantly failing or unstable 14:59:33 not ok 4145 sequential/test-http-server-request-timeouts-mixed |
#43465. Test was marked flaky on macOS in #56503 (which isn't in a release yet but is in the proposal for Node.js 23.7.0). I'd have no objections to pulling in "mark test as flaky" PRs that haven't gone out in current releases if it helps stabilize the CI situation. |
I'll cherry-pick it |
b5d87d0
to
3b08598
Compare
Finally a green CI |
Landed in 1c8b474 |
Unblocks v20 release #56699
Refs: #56726
@nodejs/platform-smartos
@nodejs/releasers