Uh oh!
There was an error while loading. Please reload this page.
test: mark test-tick-processor flaky - #4809
Conversation
jasnell
commented
Jan 22, 2016
@Trott ... is this flakiness due to recent changes or would this need to be marked in LTS also? |
Trott
commented
Jan 22, 2016
@jasnell This should apply to LTS as well. |
Trott
commented
Jan 24, 2016
CI: https://ci.nodejs.org/job/node-test-pull-request/1360/ /cc @nodejs/testing (looking for an |
jasnell
commented
Jan 24, 2016
LGTM
|
jbergstroem
commented
Jan 24, 2016
LGTM 😢 |
cjihrig
commented
Jan 24, 2016
LGTM |
PR-URL: nodejs#4809 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: James M Snell <jasnell@gmail.com> Ref: nodejs#4427
Trott
commented
Jan 25, 2016
Landed in c6d29cb |
PR-URL: nodejs#4809 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: James M Snell <jasnell@gmail.com> Ref: nodejs#4427
jasnell
commented
Jan 27, 2016
@Trott .. I marked this lts-watch for v4.. can you confirm that tho? Not sure when this went flaky |
Trott
commented
Jan 28, 2016
@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: nodejs#4809 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: James M Snell <jasnell@gmail.com> Ref: nodejs#4427
Ref: #4427
Recent sample failures: