CI Reliability 2022-08-24 #356
Comments
This was referenced Aug 24, 2022
legendecas
pushed a commit
to nodejs/node
that referenced
this issue
Aug 29, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: #44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
joyeecheung
added a commit
to nodejs/node
that referenced
this issue
Aug 31, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: #44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
joyeecheung
added a commit
to nodejs/node
that referenced
this issue
Aug 31, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: #44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 1, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: nodejs#44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 1, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: nodejs#44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 1, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: nodejs#44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 1, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: nodejs#44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 1, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: nodejs#44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 1, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: nodejs#44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 5, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: #44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 5, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: #44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 5, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: #44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 6, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: nodejs#44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
joyeecheung
added a commit
to joyeecheung/node
that referenced
this issue
Sep 6, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: nodejs#44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 6, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: #44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 6, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: #44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 7, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: #44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Sep 7, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: #44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
Fyko
pushed a commit
to Fyko/node
that referenced
this issue
Sep 15, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: nodejs#44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Fyko
pushed a commit
to Fyko/node
that referenced
this issue
Sep 15, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: nodejs#44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Fyko
pushed a commit
to Fyko/node
that referenced
this issue
Sep 15, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: nodejs#44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Sep 16, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: #44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Sep 16, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: #44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 3, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: #44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 4, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: #44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 4, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: #44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 7, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: #44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 10, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: #44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 10, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: #44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 10, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: #44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 11, 2022
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: #44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 11, 2022
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: #44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
juanarbol
pushed a commit
to nodejs/node
that referenced
this issue
Oct 11, 2022
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: #44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: nodejs/node#44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: nodejs/node#44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: nodejs/node#44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
The original heap prof tests can take too long to complete on azure Windows machines, resulting in timeouts. Split them into smaller tests and move them into the parallel directory to speed up the execution. PR-URL: nodejs/node#44388 Refs: nodejs/reliability#356 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
On Windows it might take too long for the parent to start the communication with a child process, so by the time the parent starts its own timer, the child process might have already completed running, and the parent in those tests won't have a chance to terminate these child processes after the timeout. To address this issue, raise the time for which the child is supposed to run to make sure that the parent starts its own timer before the child terminates in the tests. Also, split the test into smaller ones to reduce the overhead. PR-URL: nodejs/node#44390 Refs: nodejs/reliability#356 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
On some machines the report OOM tests can take too long to complete, resulting in a timeout. This splits the test into several different smaller tests to reduce the flakiness of it. PR-URL: nodejs/node#44389 Refs: nodejs/reliability#356 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.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
Failures in node-test-pull-request/46139 to node-test-pull-request/46230 that failed more than 2 PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)Jenkins Failure
Backing channel 'JNLP4-connect connection from ... is disconnected.Example
Build timed out (after 60 minutes). Marking the build as failed.Example
Build Failure
undefined
UnknownExample
JSTest Failure
sequential/test-child-process-execsyncExample
sequential/test-debugger-backtraceExample
sequential/test-debugger-custom-portExample
sequential/test-debugger-execExample
sequential/test-debugger-sb-before-loadExample
sequential/test-debugger-auto-resumeExample
sequential/test-debugger-exec-scopeExample
sequential/test-debugger-launchExample
sequential/test-debugger-listExample
sequential/test-debugger-preserve-breaksExample
sequential/test-debugger-random-port-with-inspect-portExample
sequential/test-debugger-run-after-quit-restartExample
sequential/test-debugger-watchersExample
sequential/test-debugger-breakExample
sequential/test-debugger-clear-breakpointsExample
sequential/test-debugger-heap-profilerExample
sequential/test-debugger-object-type-remote-objectExample
sequential/test-debugger-restart-messageExample
sequential/test-debugger-random-portExample
sequential/test-debugger-use-strictExample
sequential/test-heap-profExample
parallel/test-child-process-exec-timeoutExample
sequential/test-debugger-profileExample
parallel/test-debugger-extract-function-nameExample
report/test-report-fatalerror-oomerrorExample
sequential/test-debugger-breakpoint-existsExample
sequential/test-debugger-exceptionsExample
sequential/test-debugger-helpExample
sequential/test-debugger-low-levelExample
sequential/test-debugger-profile-commandExample
sequential/test-debugger-scriptsExample
parallel/test-child-process-spawnsync-timeoutExample
parallel/test-vm-timeout-escape-promise-2Example
sequential/test-worker-profExample
wpt/test-webcryptoExample
Progress
Backing channel 'JNLP4-connect connection from ... is disconnected.(3)Build timed out (after 60 minutes). Marking the build as failed.(2)Unknown(23)sequential/test-child-process-execsync(15) test: raise sleep times in child process tests node#44375sequential/test-debugger-backtrace(11) debugger: various fixes to the debugger and the debugger tests node#44359 (also fixes other debugger tests)sequential/test-debugger-custom-port(11)sequential/test-debugger-exec(11)sequential/test-debugger-sb-before-load(11)sequential/test-debugger-auto-resume(10)sequential/test-debugger-exec-scope(10)sequential/test-debugger-launch(10)sequential/test-debugger-list(10)sequential/test-debugger-preserve-breaks(10)sequential/test-debugger-random-port-with-inspect-port(10)sequential/test-debugger-run-after-quit-restart(10)sequential/test-debugger-watchers(10)sequential/test-debugger-break(9)sequential/test-debugger-clear-breakpoints(9)sequential/test-debugger-heap-profiler(9)sequential/test-debugger-object-type-remote-object(9)sequential/test-debugger-restart-message(9)sequential/test-debugger-random-port(8)sequential/test-debugger-use-strict(8)sequential/test-heap-prof(8) test: split heap prof tests node#44388parallel/test-child-process-exec-timeout(7) test: deflake child process exec timeout tests node#44390sequential/test-debugger-profile(7)parallel/test-debugger-extract-function-name(6)report/test-report-fatalerror-oomerror(6) test: split report OOM tests node#44389sequential/test-debugger-breakpoint-exists(5)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-scripts(5)parallel/test-child-process-spawnsync-timeout(4): test: raise sleep times in child process tests node#44375parallel/test-vm-timeout-escape-promise-2(2)sequential/test-worker-prof(2)wpt/test-webcrypto(2)The text was updated successfully, but these errors were encountered: