CI Reliability 2023-09-27 #676
Comments
This was referenced Sep 27, 2023
joyeecheung
added a commit
to nodejs/node
that referenced
this issue
Sep 29, 2023
Previously when checking the initial timing we did a lot of checks after accessing and copying timing.duration and before we check that timing.duration is roughly the same as performance.now(), which can lead to flakes if the overhead of the checking is big enough. Update the test to check timing.duration against performance.now() as soon as possible when it's copied instead of computed. :# PR-URL: #49892 Refs: nodejs/reliability#676 Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Richard Lau <[email protected]>
alexfernandez
pushed a commit
to alexfernandez/node
that referenced
this issue
Nov 1, 2023
Previously when checking the initial timing we did a lot of checks after accessing and copying timing.duration and before we check that timing.duration is roughly the same as performance.now(), which can lead to flakes if the overhead of the checking is big enough. Update the test to check timing.duration against performance.now() as soon as possible when it's copied instead of computed. :# PR-URL: nodejs#49892 Refs: nodejs/reliability#676 Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Richard Lau <[email protected]>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Nov 11, 2023
Previously when checking the initial timing we did a lot of checks after accessing and copying timing.duration and before we check that timing.duration is roughly the same as performance.now(), which can lead to flakes if the overhead of the checking is big enough. Update the test to check timing.duration against performance.now() as soon as possible when it's copied instead of computed. :# PR-URL: #49892 Refs: nodejs/reliability#676 Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Richard Lau <[email protected]>
debadree25
pushed a commit
to debadree25/node
that referenced
this issue
Apr 15, 2024
Previously when checking the initial timing we did a lot of checks after accessing and copying timing.duration and before we check that timing.duration is roughly the same as performance.now(), which can lead to flakes if the overhead of the checking is big enough. Update the test to check timing.duration against performance.now() as soon as possible when it's copied instead of computed. :# PR-URL: nodejs#49892 Refs: nodejs/reliability#676 Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Richard Lau <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failures in node-test-pull-request/54170 to node-test-pull-request/54263 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)JSTest Failure
parallel/test-inspector-scriptparsed-contextExample
parallel/test-tls-socket-closeExample
sequential/test-http-regr-gh-2928Example
sequential/test-net-connect-econnrefusedExample
sequential/test-perf-hooksExample
parallel/test-cluster-fork-stdioExample
parallel/test-fs-rmdir-recursiveExample
parallel/test-fs-write-stream-eagainExample
parallel/test-http-server-request-timeouts-mixedExample
parallel/test-inspector-consoleExample
parallel/test-inspector-debug-endExample
parallel/test-inspector-esmExample
parallel/test-inspector-multisession-wsExample
parallel/test-inspector-stop-profile-after-doneExample
parallel/test-runner-outputExample
parallel/test-tick-processor-argumentsExample
parallel/test-worker-memoryExample
pummel/test-crypto-timing-safe-equal-benchmarksExample
sequential/test-http-keepalive-maxsocketsExample
Jenkins Failure
Build timed out (after 60 minutes). Marking the build as failed.Example
CCTest Failure
Git Failure
Build Failure
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?Example
Progress
parallel/test-inspector-scriptparsed-context(3)parallel/test-tls-socket-close(3)sequential/test-http-regr-gh-2928(3)sequential/test-net-connect-econnrefused(3)sequential/test-perf-hooks(3)parallel/test-cluster-fork-stdio(2)parallel/test-fs-rmdir-recursive(2)parallel/test-fs-write-stream-eagain(2)parallel/test-http-server-request-timeouts-mixed(2)parallel/test-inspector-console(2)parallel/test-inspector-debug-end(2)parallel/test-inspector-esm(2)parallel/test-inspector-multisession-ws(2)parallel/test-inspector-stop-profile-after-done(2)parallel/test-runner-output(2)parallel/test-tick-processor-arguments(2)parallel/test-worker-memory(2)pummel/test-crypto-timing-safe-equal-benchmarks(2)sequential/test-http-keepalive-maxsockets(2)Build timed out (after 60 minutes). Marking the build as failed.(14)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3)The text was updated successfully, but these errors were encountered: