-
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-09-04 #655
Comments
nodejs-github-bot
pushed a commit
to nodejs/node
that referenced
this issue
Sep 7, 2023
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was previously timing out in CI (took more than 2 minutes) so should see a bigger gap in the CI. PR-URL: #49492 Refs: #49202 Refs: nodejs/reliability#655 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
ruyadorno
pushed a commit
to nodejs/node
that referenced
this issue
Sep 28, 2023
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was previously timing out in CI (took more than 2 minutes) so should see a bigger gap in the CI. PR-URL: #49492 Refs: #49202 Refs: nodejs/reliability#655 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
alexfernandez
pushed a commit
to alexfernandez/node
that referenced
this issue
Nov 1, 2023
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was previously timing out in CI (took more than 2 minutes) so should see a bigger gap in the CI. PR-URL: nodejs#49492 Refs: nodejs#49202 Refs: nodejs/reliability#655 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Nov 15, 2023
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was previously timing out in CI (took more than 2 minutes) so should see a bigger gap in the CI. PR-URL: #49492 Refs: #49202 Refs: nodejs/reliability#655 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
sercher
added a commit
to sercher/graaljs
that referenced
this issue
Apr 25, 2024
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was previously timing out in CI (took more than 2 minutes) so should see a bigger gap in the CI. PR-URL: nodejs/node#49492 Refs: nodejs/node#49202 Refs: nodejs/reliability#655 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
sercher
added a commit
to sercher/graaljs
that referenced
this issue
Apr 25, 2024
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was previously timing out in CI (took more than 2 minutes) so should see a bigger gap in the CI. PR-URL: nodejs/node#49492 Refs: nodejs/node#49202 Refs: nodejs/reliability#655 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Luigi Pinca <luigipinca@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/53610 to node-test-pull-request/53709 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)Jenkins Failure
Build timed out (after 60 minutes). Marking the build as failed.
Example
CCTest Failure
Value of: (!expectation.read_expected)
Example
Git Failure
ERROR: Error fetching remote repo 'origin'
Example
Build Failure
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Example
fatal: No rebase in progress?
Example
sh: line 0: printf: write error: No space left on device
Example
ERROR: Step �Publish JUnit test result report� failed: no workspace for ...
Example
fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)
Example
JSTest Failure
sequential/test-http-regr-gh-2928
Example
sequential/test-worker-prof
Example
parallel/test-blob-file-backed
Example
node-api/test_threadsafe_function/test
Example
parallel/test-inspector-stop-profile-after-done
Example
parallel/test-runner-watch-mode
Example
sequential/test-cli-syntax-require
Example
sequential/test-single-executable-application-snapshot
Example
sequential/test-single-executable-application-snapshot-and-code-cache
Example
parallel/test-crypto-dh
Example
parallel/test-http-remove-connection-header-persists-connection
Example
parallel/test-module-loading-globalpaths
Example
parallel/test-runner-output
Example
pummel/test-heapdump-shadow-realm
Example
Progress
Build timed out (after 60 minutes). Marking the build as failed.
(6)Value of: (!expectation.read_expected)
(2)ERROR: Error fetching remote repo 'origin'
(3)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
(3)fatal: No rebase in progress?
(3)sh: line 0: printf: write error: No space left on device
(3)ERROR: Step �Publish JUnit test result report� failed: no workspace for ...
(2)fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)
(2)sequential/test-http-regr-gh-2928
(7)sequential/test-worker-prof
(6)parallel/test-blob-file-backed
(4)node-api/test_threadsafe_function/test
(3)parallel/test-inspector-stop-profile-after-done
(3)parallel/test-runner-watch-mode
(3)sequential/test-cli-syntax-require
(3)sequential/test-single-executable-application-snapshot
(3)sequential/test-single-executable-application-snapshot-and-code-cache
(3)parallel/test-crypto-dh
(2)parallel/test-http-remove-connection-header-persists-connection
(2)parallel/test-module-loading-globalpaths
(2)parallel/test-runner-output
(2)pummel/test-heapdump-shadow-realm
(2)The text was updated successfully, but these errors were encountered: