-
Notifications
You must be signed in to change notification settings - Fork 13
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 2022-08-22 #354
Comments
joyeecheung
added a commit
to nodejs/node
that referenced
this issue
Sep 1, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: #44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 1, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: nodejs#44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 1, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: nodejs#44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 5, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: #44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 6, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: nodejs#44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 6, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: #44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 7, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: #44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
Fyko
pushed a commit
to Fyko/node
that referenced
this issue
Sep 15, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: nodejs#44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Sep 16, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: #44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 10, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: #44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 11, 2022
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: #44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: nodejs/node#44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
The test previously created two fs.promises.open calls on the same file with w+ back-to-back, and one of them could fail when checking the contents of that file if the other happened to be opening the file for write. Split them into different tests (with different tmpdir) to avoid the race. PR-URL: nodejs/node#44380 Refs: nodejs/reliability#354 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.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/46038 to node-test-pull-request/46131 that failed more than 2 PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)JSTest Failure
sequential/test-debugger-exceptions
Example
sequential/test-debugger-help
Example
sequential/test-debugger-low-level
Example
sequential/test-debugger-profile-command
Example
sequential/test-debugger-break
Example
sequential/test-debugger-breakpoint-exists
Example
sequential/test-debugger-heap-profiler
Example
sequential/test-debugger-list
Example
sequential/test-debugger-random-port
Example
sequential/test-debugger-sb-before-load
Example
sequential/test-debugger-scripts
Example
node-api/test_threadsafe_function/test
Example
parallel/test-vm-timeout-escape-promise-2
Example
sequential/test-debugger-custom-port
Example
sequential/test-debugger-launch
Example
sequential/test-debugger-preserve-breaks
Example
sequential/test-debugger-random-port-with-inspect-port
Example
sequential/test-debugger-run-after-quit-restart
Example
sequential/test-debugger-watchers
Example
sequential/test-heap-prof
Example
sequential/test-http-regr-gh-2928
Example
parallel/test-child-process-exec-timeout
Example
parallel/test-fs-write-stream-file-handle
Example
parallel/test-inspector-multisession-ws
Example
pummel/test-timers
Example
sequential/test-debugger-backtrace
Example
sequential/test-debugger-exec
Example
sequential/test-diagnostic-dir-cpu-prof
Example
sequential/test-perf-hooks
Example
Jenkins Failure
Backing channel 'JNLP4-connect connection from ... is disconnected.
Example
Build timed out (after 60 minutes). Marking the build as failed.
Example
Git Failure
Build Failure
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Example
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...
Example
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Example
Error: [WinError 5] Access is denied: 'C:\Users\Administrator\clcache\stats.txt.new' -> 'C:\Users\Administrator\clcache\stats.txt'
Example
undefined
Unknown
Example
Progress
sequential/test-debugger-exceptions
(5)sequential/test-debugger-help
(5)sequential/test-debugger-low-level
(5)sequential/test-debugger-profile-command
(5)sequential/test-debugger-break
(4)sequential/test-debugger-breakpoint-exists
(4)sequential/test-debugger-heap-profiler
(4)sequential/test-debugger-list
(4)sequential/test-debugger-random-port
(4)sequential/test-debugger-sb-before-load
(4)sequential/test-debugger-scripts
(4)node-api/test_threadsafe_function/test
(3)parallel/test-vm-timeout-escape-promise-2
(3)sequential/test-debugger-custom-port
(3)sequential/test-debugger-launch
(3)sequential/test-debugger-preserve-breaks
(3)sequential/test-debugger-random-port-with-inspect-port
(3)sequential/test-debugger-run-after-quit-restart
(3)sequential/test-debugger-watchers
(3)sequential/test-heap-prof
(3)sequential/test-http-regr-gh-2928
(3)parallel/test-child-process-exec-timeout
(2)parallel/test-fs-write-stream-file-handle
(2)parallel/test-inspector-multisession-ws
(2)pummel/test-timers
(2)sequential/test-debugger-backtrace
(2)sequential/test-debugger-exec
(2)sequential/test-diagnostic-dir-cpu-prof
(2)sequential/test-perf-hooks
(2)Backing channel 'JNLP4-connect connection from ... is disconnected.
(4)Build timed out (after 60 minutes). Marking the build as failed.
(2)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
(2)ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...
(2)ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
(2)Error: [WinError 5] Access is denied: 'C:\\Users\\Administrator\\clcache\\stats.txt.new' -> 'C:\\Users\\Administrator\\clcache\\stats.txt'
(2)Unknown
(16)The text was updated successfully, but these errors were encountered: