CI Reliability 2022-08-05 #337

github-actions · 2022-08-05T00:16:55Z

Failures in node-test-pull-request/45748 to node-test-pull-request/45844 that failed more than 2 PRs
(Generated with ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)

UTC Time	RUNNING	SUCCESS	UNSTABLE	ABORTED	FAILURE	Green Rate
2022-08-05 00:16	2	8	31	3	56	8.42%

Jenkins Failure

Reason	`Backing channel 'JNLP4-connect connection from ... is disconnected.`
Type	JENKINS_FAILURE
Failed PR	7 (nodejs/node#44075, nodejs/node#44081, nodejs/node#44080, nodejs/node#38905, nodejs/node#44091, nodejs/node#44110, nodejs/node#44129)
Appeared	test-nearform-macos11.0-arm64-1, test-azure_msft-win10_vs2019-x64-1, test-digitalocean-freebsd12-x64-2, test-nearform-macos10.15-x64-3
First CI	https://ci.nodejs.org/job/node-test-pull-request/45761/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45837/

Example

java.io.IOException: Backing channel 'JNLP4-connect connection from ip-83-147-191-75.broadband.digiweb.ie/83.147.191.75:62172' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
	at com.sun.proxy.$Proxy79.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)

Git Failure

Build Failure

Reason	`ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...`
Type	BUILD_FAILURE
Failed PR	4 (nodejs/node#44080, nodejs/node#44129, nodejs/node#44132, nodejs/node#44102)
Appeared	test-nearform-macos10.15-x64-3, test-digitalocean-freebsd12-x64-2
First CI	https://ci.nodejs.org/job/node-test-pull-request/45812/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45842/

Example

ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-osx/nodes=osx1015 #46644
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason	`ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?`
Type	BUILD_FAILURE
Failed PR	2 (nodejs/node#44080, nodejs/node#44132)
Appeared	test-equinix-debian10_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/45805/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45840/

Example

ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
[PostBuildScript] - [INFO] Executing post build scripts.
[node-test-binary-armv7l] $ /bin/bash -ex /tmp/jenkins7034929457788994109.sh
+ '[' -d .git ']'
+ git clean -fdx
Removing config.gypi

Reason	`Error: Not supported`
Type	BUILD_FAILURE
Failed PR	2 (nodejs/node#44079, nodejs/node#44048)
Appeared	test-joyent-smartos18-x64-3
First CI	https://ci.nodejs.org/job/node-test-pull-request/45782/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45794/

Example

Error: Not supported
    at vm:module(0):1:1
    at SourceTextModule.evaluate (internal/vm/module.js:222:32)
    at embedder_main_7.js:1:328
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:37543) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

Reason	`fatal error: ld terminated with signal 9 [Killed]`
Type	BUILD_FAILURE
Failed PR	2 (nodejs/node#44085, nodejs/node#44075)
Appeared	test-digitalocean-ubuntu1804_sharedlibs_container-x64-8
First CI	https://ci.nodejs.org/job/node-test-pull-request/45774/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45776/

Example

fatal error: ld terminated with signal 9 [Killed]

undefined

Reason	`Unknown`
Type	undefined
Failed PR	16 (nodejs/node#43904, nodejs/node#44056, nodejs/node#44077, nodejs/node#44060, nodejs/node#44081, nodejs/node#44075, nodejs/node#44048, nodejs/node#38905, nodejs/node#44074, nodejs/node#44090, nodejs/node#44080, nodejs/node#44110, nodejs/node#44101, nodejs/node#44109, nodejs/node#44132, nodejs/node#44102)
Appeared	test-nearform_arm-win10_vs2019-arm64-1, test-equinix-debian10_container-armv7l-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/45750/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45842/

Example

Unknown

JSTest Failure

Reason	`parallel/test-worker-fshandles-error-on-termination`
Type	JS_TEST_FAILURE
Failed PR	8 (nodejs/node#44070, nodejs/node#44079, nodejs/node#44077, nodejs/node#44085, nodejs/node#44075, nodejs/node#44078, nodejs/node#44069, nodejs/node#44129)
Appeared	test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-digitalocean-alpine312_container-x64-2, test-digitalocean-alpine311_container-x64-2, test-softlayer-alpine312_container-x64-1, test-digitalocean-ubi81_container-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-5, test-digitalocean-ubuntu1804_sharedlibs_container-x64-10, test-digitalocean-ubuntu1804_sharedlibs_container-x64-7, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-softlayer-ubuntu1804_sharedlibs_container-x64-2, test-softlayer-ubuntu1804_sharedlibs_container-x64-3, test-softlayer-ubi81_container-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-1, test-digitalocean-alpine311_container-x64-1, test-digitalocean-alpine312_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-5
First CI	https://ci.nodejs.org/job/node-test-pull-request/45756/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45837/

Example

not ok 2983 parallel/test-worker-fshandles-error-on-termination
  ---
  duration_ms: 120.120
  severity: fail
  stack: |-
    timeout
  ...

Reason	`parallel/test-worker-fshandles-open-close-on-termination`
Type	JS_TEST_FAILURE
Failed PR	8 (nodejs/node#44070, nodejs/node#44079, nodejs/node#44077, nodejs/node#44085, nodejs/node#44078, nodejs/node#44075, nodejs/node#44069, nodejs/node#44101)
Appeared	test-rackspace-win2012r2_vs2019-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-rackspace-win2012r2_vs2015-x64-2, test-digitalocean-alpine312_container-x64-2, test-digitalocean-alpine311_container-x64-2, test-softlayer-alpine312_container-x64-1, test-digitalocean-ubi81_container-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-5, test-digitalocean-ubuntu1804_sharedlibs_container-x64-10, test-digitalocean-ubuntu1804_sharedlibs_container-x64-7, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-softlayer-ubuntu1804_sharedlibs_container-x64-2, test-softlayer-ubuntu1804_sharedlibs_container-x64-3, test-softlayer-ubi81_container-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-1, test-digitalocean-alpine311_container-x64-1, test-digitalocean-alpine312_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-5, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3
First CI	https://ci.nodejs.org/job/node-test-pull-request/45756/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45818/

Example

not ok 790 parallel/test-worker-fshandles-open-close-on-termination
  ---
  duration_ms: 1.343
  severity: fail
  exitcode: 3221226356
  stack: |-
  ...

Reason	`parallel/test-diagnostics-channel-net`
Type	JS_TEST_FAILURE
Failed PR	5 (nodejs/node#44080, nodejs/node#44091, nodejs/node#44090, nodejs/node#44048, nodejs/node#44018)
Appeared	undefined
First CI	https://ci.nodejs.org/job/node-test-pull-request/45809/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45822/

Example

not ok 818 parallel/test-diagnostics-channel-net
  ---
  duration_ms: 0.427
  severity: fail
  exitcode: 1
  stack: |-
    Mismatched <anonymous> function calls. Expected exactly 1, actual 0.
  ...

Reason	`parallel/test-heapsnapshot-near-heap-limit-worker`
Type	JS_TEST_FAILURE
Failed PR	5 (nodejs/node#44080, nodejs/node#44090, nodejs/node#44110, nodejs/node#44109, nodejs/node#44102)
Appeared	test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-6, test-rackspace-win2012r2_vs2019-x64-5
First CI	https://ci.nodejs.org/job/node-test-pull-request/45791/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45842/

Example

not ok 328 parallel/test-heapsnapshot-near-heap-limit-worker
  ---
  duration_ms: 4.506
  severity: fail
  exitcode: 1
  stack: |-
    
    Invoked NearHeapLimitCallback, processing=false, current_limit=52428800, initial_limit=52428800
    max_young_gen_size=25165824, young_gen_size=0, old_gen_size=51250696, total_size=51250696
    Estimated available memory=6149320704, estimated overhead=25165824
    Start generating Heap.20220804.165945.4268.1.001.heapsnapshot...
    Wrote snapshot to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.291\Heap.20220804.165945.4268.1.001.heapsnapshot
    
    <--- Last few GCs --->
    
    [4268:06503560]     2753 ms: Mark-sweep (reduce) 48.8 (52.8) -> 48.8 (52.8) MB, 6.2 / 0.0 ms  (average mu = 0.333, current mu = -0.150) heap profiler; GC in old space requested
    
    
    <--- JS stacktrace --->
    
    FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
     1: 012FEB2B v8::internal::Heap::PageFlagsAreC...

Reason	`parallel/test-vm-break-on-sigint`
Type	JS_TEST_FAILURE
Failed PR	5 (nodejs/node#44070, nodejs/node#44085, nodejs/node#44082, nodejs/node#44098, nodejs/node#44129)
Appeared	test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-5, test-digitalocean-ubuntu1804_sharedlibs_container-x64-1, test-softlayer-ubi81_container-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-10
First CI	https://ci.nodejs.org/job/node-test-pull-request/45756/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45837/

Example

not ok 2975 parallel/test-vm-break-on-sigint
  ---
  duration_ms: 120.90
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

Reason	`parallel/test-debugger-extract-function-name`
Type	JS_TEST_FAILURE
Failed PR	3 (nodejs/node#44077, nodejs/node#44080, nodejs/node#44101)
Appeared	test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vs2019-x64-4
First CI	https://ci.nodejs.org/job/node-test-pull-request/45765/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45824/

Example

not ok 211 parallel/test-debugger-extract-function-name
  ---
  duration_ms: 6.632
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (5000) while waiting for /break (?:on start )?in/i; found: connecting to 127.0.0.1:9229 ...
    < Debugger listening on ws://127.0.0.1:9229/450b2df8-6f0d-4846-823b-4108f2c3d0e6
    < 
    
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    
     ok
    < Debugger attached.
    < 
    
    debug> 
        at Timeout.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84:18)
        at listOnTimeout (node:internal/timers:564:17)
        at process.processTimers (node:internal/timers:507:7)
    
    Node.js v19.0.0-pre
  ...

Reason	`parallel/test-fs-stat-date`
Type	JS_TEST_FAILURE
Failed PR	3 (nodejs/node#44070, nodejs/node#44081, nodejs/node#44129)
Appeared	test-requireio_joeyvandijk-debian10-armv7l_pi2-2, test-requireio_williamkapke-debian10-arm64_pi3-3, test-requireio_mininodes-debian10-armv7l_pi2-1, test-requireio_securogroup-debian10-arm64_pi3-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/45767/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45834/

Example

not ok 267 parallel/test-fs-stat-date
  ---
  duration_ms: 2.476
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/process/esm_loader:97
        internalBinding('errors').triggerUncaughtException(
                                  ^
    
    AssertionError [ERR_ASSERTION]: expected 1 ± 2.220446049250313e-16, got 0
        at closeEnough (file:///home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-stat-date.mjs:26:10)
        at runTest (file:///home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-stat-date.mjs:40:3)
        at async file:///home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-stat-date.mjs:76:3 {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
  ...

Reason	`parallel/test-crypto-secure-heap`
Type	JS_TEST_FAILURE
Failed PR	2 (nodejs/node#44090, nodejs/node#44129)
Appeared	test-digitalocean-freebsd12-x64-2
First CI	https://ci.nodejs.org/job/node-test-pull-request/45813/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45834/

Example

not ok 451 parallel/test-crypto-secure-heap
  ---
  duration_ms: 0.407
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:1027
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The input did not match the regular expression /--secure-heap must be a power of 2/. Input:
    
    ''
    
        at ChildProcess.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/parallel/test-crypto-secure-heap.js:71:12)
        at ChildProcess.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/common/index.js:420:15)
        at ChildProcess.emit (node:events:513:28)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '',
      expected: /--secure-heap must be a power of 2/,
      operator: 'match'
    }
  ...

Reason	`parallel/test-vm-timeout-escape-promise-2`
Type	JS_TEST_FAILURE
Failed PR	2 (nodejs/node#44098, nodejs/node#44074)
Appeared	test-ibm-rhel7-s390x-3
First CI	https://ci.nodejs.org/job/node-test-pull-request/45799/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45801/

Example

not ok 3006 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 0.274
  severity: fail
  exitcode: 1
  stack: |-
    /home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:20
          throw new Error(
                ^
    
    Error: escaped timeout at 100 milliseconds!
        at loop (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:20:13)
        at evalmachine.<anonymous>:1:30
        at Script.runInContext (node:vm:141:12)
        at Script.runInNewContext (node:vm:146:17)
        at Object.runInNewContext (node:vm:306:38)
        at assert.throws.code (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:27:6)
        at getActual (node:assert:757:5)
        at Function.throws (node:assert:903:24)
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:26:8)
      ...

Reason	`parallel/test-worker-heap-snapshot`
Type	JS_TEST_FAILURE
Failed PR	2 (nodejs/node#43904, nodejs/node#44080)
Appeared	test-rackspace-win2012r2_vs2017-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-8
First CI	https://ci.nodejs.org/job/node-test-pull-request/45749/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45815/

Example

not ok 794 parallel/test-worker-heap-snapshot
  ---
  duration_ms: 1.362
  severity: fail
  exitcode: 134
  stack: |-
    FATAL ERROR: HandleScope::HandleScope Entering the V8 API without proper locking in place
  ...

Reason	`sequential/test-worker-prof`
Type	JS_TEST_FAILURE
Failed PR	2 (nodejs/node#43904, nodejs/node#44060)
Appeared	test-azure_msft-win10_vs2019-x64-1, test-rackspace-win2012r2_vs2019-x64-4
First CI	https://ci.nodejs.org/job/node-test-pull-request/45750/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/45768/

Example

not ok 879 sequential/test-worker-prof
  ---
  duration_ms: 2.680
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:124
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child exited with non-zero status:                      {
      status: 3221225477,
      signal: null,
      output: [ null, '', '' ],
      pid: 10288,
      stdout: '',
      stderr: ''
    }
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:61:10)
        at Module._compile (node:internal/modules/cjs/loader:1120:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
        at Module.load (node:internal/modules/cjs/loader:998:32)
        at Module._load (node:internal/modules/cjs/loader:839:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12)
        at node:internal/main/run_main_module:17:47 {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
 ...

Progress

The text was updated successfully, but these errors were encountered:

This PR moves `test-vm-break-on-sigint.js` to sequential, following the other PRs I have made to move CPU intensive tests into sequential. The test has already been tuned to do less iterations in a previous PR. However it is still causing ~7% of build failures. The timeouts seem highly correlated with other tests which spawn a bunch of threads also failing, see for example the [first Jenkins failure][] and the [last Jenkins failure][]. [first Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45756/ [last Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45837/ Refs: nodejs#44090 Refs: nodejs#43981 Refs: nodejs/reliability#337

This PR moves `test-vm-break-on-sigint.js` to sequential, following the other PRs I have made to move CPU intensive tests into sequential. The test has already been tuned to do less iterations in a previous PR. However it is still causing ~7% of build failures. The timeouts seem highly correlated with other tests which spawn a bunch of threads also failing, see for example the [first Jenkins failure][] and the [last Jenkins failure][]. [first Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45756/ [last Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45837/ Refs: #44090 Refs: #43981 Refs: nodejs/reliability#337 PR-URL: #44140 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: theanarkh <theratliter@gmail.com> Reviewed-By: Feng Yu <F3n67u@outlook.com>

This PR moves `test-vm-break-on-sigint.js` to sequential, following the other PRs I have made to move CPU intensive tests into sequential. The test has already been tuned to do less iterations in a previous PR. However it is still causing ~7% of build failures. The timeouts seem highly correlated with other tests which spawn a bunch of threads also failing, see for example the [first Jenkins failure][] and the [last Jenkins failure][]. [first Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45756/ [last Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45837/ Refs: nodejs#44090 Refs: nodejs#43981 Refs: nodejs/reliability#337 PR-URL: nodejs#44140 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: theanarkh <theratliter@gmail.com> Reviewed-By: Feng Yu <F3n67u@outlook.com>

This PR moves `test-vm-break-on-sigint.js` to sequential, following the other PRs I have made to move CPU intensive tests into sequential. The test has already been tuned to do less iterations in a previous PR. However it is still causing ~7% of build failures. The timeouts seem highly correlated with other tests which spawn a bunch of threads also failing, see for example the [first Jenkins failure][] and the [last Jenkins failure][]. [first Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45756/ [last Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45837/ Refs: #44090 Refs: #43981 Refs: nodejs/reliability#337 PR-URL: #44140 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: theanarkh <theratliter@gmail.com> Reviewed-By: Feng Yu <F3n67u@outlook.com>

This PR moves `test-vm-break-on-sigint.js` to sequential, following the other PRs I have made to move CPU intensive tests into sequential. The test has already been tuned to do less iterations in a previous PR. However it is still causing ~7% of build failures. The timeouts seem highly correlated with other tests which spawn a bunch of threads also failing, see for example the [first Jenkins failure][] and the [last Jenkins failure][]. [first Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45756/ [last Jenkins failure]: https://ci.nodejs.org/job/node-test-pull-request/45837/ Refs: nodejs/node#44090 Refs: nodejs/node#43981 Refs: nodejs/reliability#337 PR-URL: nodejs/node#44140 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: theanarkh <theratliter@gmail.com> Reviewed-By: Feng Yu <F3n67u@outlook.com>

This was referenced Aug 5, 2022

test: move test-vm-break-on-sigint to sequential nodejs/node#44140

Merged

flaky test.parallel/test-diagnostics-channel-net nodejs/node#44143

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CI Reliability 2022-08-05 #337

CI Reliability 2022-08-05 #337

github-actions bot commented Aug 5, 2022

CI Reliability 2022-08-05 #337

CI Reliability 2022-08-05 #337

Comments

github-actions bot commented Aug 5, 2022

Jenkins Failure

Git Failure

Build Failure

undefined

JSTest Failure

Progress