-
Notifications
You must be signed in to change notification settings - Fork 11
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
CI Reliability 2023-08-16 #638
Comments
nodejs-github-bot
pushed a commit
to nodejs/node
that referenced
this issue
Aug 18, 2023
Previously the test makes several assumptions about the absolute values of the nodeTiming fields, which can make the test flaky on slow machines. This patch rewrites the test to check the relative values instead. It also updates the test to make it work with workers instead of directly skipping in workers. PR-URL: #49197 Refs: nodejs/reliability#638 Reviewed-By: Debadree Chatterjee <debadree333@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
UlisesGascon
pushed a commit
to nodejs/node
that referenced
this issue
Sep 10, 2023
Previously the test makes several assumptions about the absolute values of the nodeTiming fields, which can make the test flaky on slow machines. This patch rewrites the test to check the relative values instead. It also updates the test to make it work with workers instead of directly skipping in workers. PR-URL: #49197 Refs: nodejs/reliability#638 Reviewed-By: Debadree Chatterjee <debadree333@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Nov 27, 2023
Previously the test makes several assumptions about the absolute values of the nodeTiming fields, which can make the test flaky on slow machines. This patch rewrites the test to check the relative values instead. It also updates the test to make it work with workers instead of directly skipping in workers. PR-URL: #49197 Refs: nodejs/reliability#638 Reviewed-By: Debadree Chatterjee <debadree333@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
sercher
added a commit
to sercher/graaljs
that referenced
this issue
Apr 25, 2024
Previously the test makes several assumptions about the absolute values of the nodeTiming fields, which can make the test flaky on slow machines. This patch rewrites the test to check the relative values instead. It also updates the test to make it work with workers instead of directly skipping in workers. PR-URL: nodejs/node#49197 Refs: nodejs/reliability#638 Reviewed-By: Debadree Chatterjee <debadree333@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
sercher
added a commit
to sercher/graaljs
that referenced
this issue
Apr 25, 2024
Previously the test makes several assumptions about the absolute values of the nodeTiming fields, which can make the test flaky on slow machines. This patch rewrites the test to check the relative values instead. It also updates the test to make it work with workers instead of directly skipping in workers. PR-URL: nodejs/node#49197 Refs: nodejs/reliability#638 Reviewed-By: Debadree Chatterjee <debadree333@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Failures in node-test-pull-request/53266 to node-test-pull-request/53361 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)Jenkins Failure
CCTest Failure
C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)
Example
Build Failure
fatal: No rebase in progress?
Example
JSTest Failure
sequential/test-net-connect-econnrefused
Example
wpt/test-structured-clone
Example
sequential/test-perf-hooks
Example
parallel/test-tls-ticket-cluster
Example
parallel/test-runner-output
Example
sequential/test-single-executable-application-snapshot
Example
sequential/test-single-executable-application-use-code-cache
Example
sequential/test-worker-prof
Example
es-module/test-esm-loader-hooks
Example
parallel/test-crypto-dh
Example
parallel/test-inspector-stop-profile-after-done
Example
sequential/test-cli-syntax-require
Example
sequential/test-single-executable-application-disable-experimental-sea-warning
Example
sequential/test-single-executable-application-empty
Example
parallel/test-debugger-break
Example
parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
Example
parallel/test-inspector-async-stack-traces-set-interval
Example
parallel/test-inspector-exception
Example
parallel/test-inspector-wait-for-connection
Example
parallel/test-vm-sigint-existing-handler
Example
pummel/test-fs-readfile-tostring-fail
Example
sequential/test-single-executable-application
Example
Progress
C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)
(2)fatal: No rebase in progress?
(2)sequential/test-net-connect-econnrefused
(9)wpt/test-structured-clone
(7)sequential/test-perf-hooks
(6)parallel/test-tls-ticket-cluster
(5)parallel/test-runner-output
(4)sequential/test-single-executable-application-snapshot
(4)sequential/test-single-executable-application-use-code-cache
(4)sequential/test-worker-prof
(4)es-module/test-esm-loader-hooks
(3)parallel/test-crypto-dh
(3)parallel/test-inspector-stop-profile-after-done
(3)sequential/test-cli-syntax-require
(3)sequential/test-single-executable-application-disable-experimental-sea-warning
(3)sequential/test-single-executable-application-empty
(3)parallel/test-debugger-break
(2)parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
(2)parallel/test-inspector-async-stack-traces-set-interval
(2)parallel/test-inspector-exception
(2)parallel/test-inspector-wait-for-connection
(2)parallel/test-vm-sigint-existing-handler
(2)pummel/test-fs-readfile-tostring-fail
(2)sequential/test-single-executable-application
(2)The text was updated successfully, but these errors were encountered: