-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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-tick-processor flaky #4809
Conversation
@Trott ... is this flakiness due to recent changes or would this need to be marked in LTS also? |
@jasnell This should apply to LTS as well. |
CI: https://ci.nodejs.org/job/node-test-pull-request/1360/ /cc @nodejs/testing (looking for an |
LGTM
|
LGTM 😢 |
LGTM |
PR-URL: nodejs#4809 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]> Ref: nodejs#4427
Landed in c6d29cb |
PR-URL: #4809 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]> Ref: #4427
PR-URL: nodejs#4809 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]> Ref: nodejs#4427
@Trott .. I marked this lts-watch for v4.. can you confirm that tho? Not sure when this went flaky |
@jasnell I ran a stress test against the v4.x branch and the test is flaky there, so yes, confirmed. https://ci.nodejs.org/job/node-stress-single-test/377/nodes=win2008r2/console |
PR-URL: #4809 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]> Ref: #4427
PR-URL: #4809 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]> Ref: #4427
PR-URL: #4809 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]> Ref: #4427
PR-URL: nodejs#4809 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]> Ref: nodejs#4427
Ref: #4427
Recent sample failures: