-
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-22 #673
Comments
This was referenced Sep 25, 2023
nodejs-github-bot
pushed a commit
to nodejs/node
that referenced
this issue
Sep 25, 2023
This has been flaky on many platforms for months. Mark it as flaky for now to avoid blocking the CI. PR-URL: #49854 Refs: #49853 Refs: nodejs/reliability#673 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
ruyadorno
pushed a commit
to nodejs/node
that referenced
this issue
Sep 28, 2023
This has been flaky on many platforms for months. Mark it as flaky for now to avoid blocking the CI. PR-URL: #49854 Refs: #49853 Refs: nodejs/reliability#673 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
ruyadorno
pushed a commit
to nodejs/node
that referenced
this issue
Sep 28, 2023
This has been flaky on many platforms for months. Mark it as flaky for now to avoid blocking the CI. PR-URL: #49854 Refs: #49853 Refs: nodejs/reliability#673 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
alexfernandez
pushed a commit
to alexfernandez/node
that referenced
this issue
Nov 1, 2023
This has been flaky on many platforms for months. Mark it as flaky for now to avoid blocking the CI. PR-URL: nodejs#49854 Refs: nodejs#49853 Refs: nodejs/reliability#673 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> 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/54045 to node-test-pull-request/54143 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)JSTest Failure
es-module/test-vm-contextified-script-leak
Example
parallel/test-runner-output
Example
parallel/test-tls-socket-close
Example
wpt/test-structured-clone
Example
parallel/test-fs-watch-recursive-update-file
Example
parallel/test-inspector-async-stack-traces-promise-then
Example
parallel/test-performance-function
Example
parallel/test-worker-memory
Example
sequential/test-vm-timeout-escape-promise-module-2
Example
Jenkins Failure
Build timed out (after 60 minutes). Marking the build as failed.
Example
Git Failure
ERROR: Error fetching remote repo 'origin'
Example
Command "git fetch --no-tags --progress git@github.com:nodejs/node.git +refs/heads/:refs/remotes/origin/ +refs/heads/v16.x-staging:refs/remotes/origin/_jenkins_local_branch" returned status code 128:
Example
Build Failure
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Example
error: The last gc run reported the following. Please correct the root cause
Example
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
Example
fatal: No rebase in progress?
Example
CCTest Failure
Value of: (!expectation.read_expected)
Example
Progress
es-module/test-vm-contextified-script-leak
(3)parallel/test-runner-output
(3)parallel/test-tls-socket-close
(3)wpt/test-structured-clone
(3)parallel/test-fs-watch-recursive-update-file
(2)parallel/test-inspector-async-stack-traces-promise-then
(2)parallel/test-performance-function
(2)parallel/test-worker-memory
(2)sequential/test-vm-timeout-escape-promise-module-2
(2)Build timed out (after 60 minutes). Marking the build as failed.
(9)ERROR: Error fetching remote repo 'origin'
(21)Command "git fetch --no-tags --progress git@github.com:nodejs/node.git +refs/heads/*:refs/remotes/origin/* +refs/heads/v16.x-staging:refs/remotes/origin/_jenkins_local_branch" returned status code 128:
(14)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
(9)error: The last gc run reported the following. Please correct the root cause
(4)fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
(4)fatal: No rebase in progress?
(2)Value of: (!expectation.read_expected)
(2)The text was updated successfully, but these errors were encountered: