CI Reliability 2023-07-31

Open
#629 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, shell

Research direction

Start with the generated ncu-ci walk pr --stats=true --markdown ... report and inspect the linked Jenkins console logs. Reproduce the named failures, including test/parallel/test-inspector-open-dispose.mjs, test/sequential/test-perf-hooks, and wpt/test-structured-clone; done means the recurring CI failures are understood and no longer cause affected pull requests to fail.

Written by the indexing model from the issue text.

Description

Failures in node-test-pull-request/52903 to node-test-pull-request/52991 that failed 2 or more 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
2023-07-31 00:13 12 0 21 18 49 0.00%
Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 7 (https://github.com/nodejs/node/pull/48896/, https://github.com/nodejs/node/pull/48033/, https://github.com/nodejs/node/pull/48925/, https://github.com/nodejs/node/pull/48607/, https://github.com/nodejs/node/pull/48942/, https://github.com/nodejs/node/pull/48663/, https://github.com/nodejs/node/pull/48698/)
Appeared test-azure_msft-win2022_vs2019-x64-4, test-azure_msft-win2022_vs2019-x64-1, test-azure_msft-win11_vs2022-arm64-3, test-azure_msft-win11_vs2022-arm64-1, test-rackspace-win2012r2_vs2019-x64-2, test-rackspace-fedora32-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/52909/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52991/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 20.106.250.216/20.106.250.216:3009' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy76.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1215)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1207)

Reason Build timed out (after 30 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/48942/, https://github.com/nodejs/node/pull/48528/)
Appeared test-ibm-rhel8-s390x-1, test-ibm-ubuntu1804-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/52960/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52973/
Example
Build timed out (after 30 minutes). Marking the build as failed.

Build Failure
Reason fatal error: Killed signal terminated program cc1plus
Type BUILD_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/48874/, https://github.com/nodejs/node/pull/46662/, https://github.com/nodejs/node/pull/48663/, https://github.com/nodejs/node/pull/48933/, https://github.com/nodejs/node/pull/48740/)
Appeared test-rackspace-fedora32-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/52905/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52963/
Example
fatal error: Killed signal terminated program cc1plus

Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/48244/, https://github.com/nodejs/node/pull/48607/)
Appeared test-ibm-aix72-ppc64_be-2, test-equinix-rhel8_container-arm64-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-6, test-equinix-ubuntu2004_container-arm64-1, test-equinix-ubuntu2004_container-armv7l-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/52949/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52959/
Example
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Sending e-mails to: michael_dawson@ca.ibm.com vieuxtech@gmail.com ashley.cripps@ibm.com
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

JSTest Failure
Reason parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/48698/, https://github.com/nodejs/node/pull/48928/, https://github.com/nodejs/node/pull/48942/, https://github.com/nodejs/node/pull/48528/, https://github.com/nodejs/node/pull/48890/)
Appeared test-ibm-rhel8-s390x-4, test-ibm-rhel8-s390x-1
First CI https://ci.nodejs.org/job/node-test-pull-request/52933/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52968/
Example
not ok 1353 parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
  ---
  duration_ms: 120066.85600
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-inspector-open-dispose
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/48611/, https://github.com/nodejs/node/pull/48698/, https://github.com/nodejs/node/pull/45704/, https://github.com/nodejs/node/pull/48929/)
Appeared test-azure_msft-win2016_vs2017-x64-1, test-rackspace-win2022_vs2022-x64-1, test-azure_msft-win2016_vs2017-x64-6, test-azure_msft-win2016_vs2017-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/52917/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52950/
Example
not ok 487 parallel/test-inspector-open-dispose
  ---
  duration_ms: 388.00700
  severity: fail
  exitcode: 1
  stack: |-
    Debugger listening on ws://127.0.0.1:51011/0f1ce0bc-a35e-469a-8c3b-fe72082bd269
    For help, see: https://nodejs.org/en/docs/inspector
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: undefined == true
        at file:///C:/workspace/node-test-binary-windows-js-suites/node/test/parallel/test-inspector-open-dispose.mjs:38:7
        at Socket.<anonymous> (file:///C:/workspace/node-test-binary-windows-js-suites/node/test/parallel/test-inspector-open-dispose.mjs:58:28)
        at Socket.emit (node:events:514:28)
        at TCP.<anonymous> (node:net:337:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: undefined,
      expected: true,
      operator: '=='
    }
    
    Node.js v21.0.0-pre
  ...


Reason sequential/test-perf-hooks
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/48880/, https://github.com/nodejs/node/pull/48698/, https://github.com/nodejs/node/pull/48929/, https://github.com/nodejs/node/pull/48528/)
Appeared test-osuosl-ubuntu2004_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-2, test-equinix-ubuntu2004_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/52908/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52961/
Example
not ok 3723 sequential/test-perf-hooks
  ---
  duration_ms: 713.53200
  severity: fail
  exitcode: 1
  stack: |-
    {
      name: 'node',
      entryType: 'node',
      startTime: 0,
      duration: { around: 483.52711486816406 },
      nodeStart: { around: 0 },
      v8Start: { around: 0 },
      bootstrapComplete: { around: 483.3923683166504, delay: 2500 },
      environment: { around: 0 },
      loopStart: -1,
      loopExit: -1
    }
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: environment: 272.0879440307617 >= 250
        at checkNodeTiming (/home/iojs/build/workspace/node-test-binary-armv7l/test/sequential/test-perf-hooks.js:31:7)
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-binary-armv7l/test/sequential/test-perf-hooks.js:43:1)
        at Module._compile (node:internal/modules/cjs/loader:1241:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
        at Module.load (node:internal/modules/cjs/loader:1091:3...

Reason wpt/test-structured-clone
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/48191/, https://github.com/nodejs/node/pull/48913/, https://github.com/nodejs/node/pull/48663/, https://github.com/nodejs/node/pull/48528/)
Appeared test-softlayer-debian10-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-5, test-orka-macos11-x64-2, test-osuosl-ubuntu2004_container-armv7l-1, test-rackspace-win2012r2_vs2015-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/52927/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52973/
Example
not ok 3883 wpt/test-structured-clone
  ---
  duration_ms: 278.93600
  severity: fail
  exitcode: 1
  stack: |-
    [PASS] primitive undefined
    [PASS] primitive null
    [PASS] primitive true
    [PASS] primitive false
    [PASS] primitive string, empty string
    [PASS] primitive string, lone high surrogate
    [PASS] primitive string, lone low surrogate
    [PASS] primitive string, NUL
    [PASS] primitive string, astral character
    [PASS] primitive number, 0.2
    [PASS] primitive number, 0
    [PASS] primitive number, -0
    [PASS] primitive number, NaN
    [PASS] primitive number, Infinity
    [PASS] primitive number, -Infinity
    [PASS] primitive number, 9007199254740992
    [PASS] primitive number, -9007199254740992
    [PASS] primitive number, 9007199254740994
    [PASS] primitive number, -9007199254740994
    [PASS] primitive BigInt, 0n
    [PASS] primitive BigInt, -0n
    [PASS] primitive BigInt, -9007199254740994000n
    [PASS] primitive BigInt, -9007199254740994000900719925474099400090071992...

Reason parallel/test-crypto-dh
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/48928/, https://github.com/nodejs/node/pull/48925/, https://github.com/nodejs/node/pull/48890/)
Appeared test-azure_msft-win11_vs2022-arm64-5, test-azure_msft-win2016_vs2017-x64-6, test-azure_msft-win2016_vs2017-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/52939/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52968/
Example
not ok 904 parallel/test-crypto-dh
  ---
  duration_ms: 120160.63800
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason sequential/test-worker-prof
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/48033/, https://github.com/nodejs/node/pull/48698/, https://github.com/nodejs/node/pull/48607/)
Appeared test-azure_msft-win2016_vs2017-x64-5, test-azure_msft-win2022_vs2019-x64-1, test-rackspace-win2012r2_vs2019-x64-2, test-azure_msft-win2016_vs2017-x64-2, test-rackspace-win2022_vs2022-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/52918/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52959/
Example
not ok 937 sequential/test-worker-prof
  ---
  duration_ms: 30262.19900
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child exited with signal: {
      error: Error: spawnSync C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe ETIMEDOUT
          at Object.spawnSync (node:internal/child_process:1124:20)
          at spawnSync (node:child_process:876:24)
          at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:53:23)
          at Module._compile (node:internal/modules/cjs/loader:1241:14)
          at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
          at Module.load (node:internal/modules/cjs/loader:1091:32)
          at Module._load (node:internal/modules/cjs/loader:938:12)
          at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
          at node:internal/main/ru...

Reason node-api/test_threadsafe_function/test
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/48663/, https://github.com/nodejs/node/pull/48740/)
Appeared test-equinix-ubuntu2004_container-armv7l-2
First CI https://ci.nodejs.org/job/node-test-pull-request/52915/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52963/
Example
not ok 138 node-api/test_threadsafe_function/test
  ---
  duration_ms: 360034.36500
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-debugger-exceptions
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/48874/, https://github.com/nodejs/node/pull/48740/)
Appeared test-azure_msft-win2016_vs2017-x64-2, test-azure_msft-win2016_vs2017-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/52906/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52955/
Example
not ok 347 parallel/test-debugger-exceptions
  ---
  duration_ms: 15567.92600
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:90
              reject(new Error([
                     ^
    
    Error: Timeout (15000) while waiting for /(?:assert|break|break on start|debugCommand|exception|other|promiseRejection) in/i; found: 
    < Debugger ending on ws://127.0.0.1:61759/fa460568-477a-43a5-b5e1-278dcbbecc10
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    debug> 
    
    < Debugger listening on ws://127.0.0.1:61762/c1ea004b-eb91-4330-a5fb-8ea8a04a937c
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    debug> 
    connecting to 127.0.0.1:61762 ...
     ok
    
    debug> 
    < Debugger attached.
    < 
    debug> 
        at Timeout.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:90:18)
        at listOnTimeout (node:internal/timers:573:17)
        at pro...

Reason parallel/test-runner-output
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/48925/, https://github.com/nodejs/node/pull/48913/)
Appeared test-azure_msft-win11_vs2022-arm64-3, test-azure_msft-win11_vs2022-arm64-1, test-rackspace-win2012r2_vs2015-x64-2, test-azure_msft-win2016_vs2017-x64-5, test-rackspace-win2019_vs2019-x64-2, test-azure_msft-win2022_vs2019-x64-2, test-digitalocean-fedora38-x64-2, test-orka-macos11-x64-2, undefined, test-rackspace-win2012r2_vs2019-x64-1, test-azure_msft-win2016_vs2017-x64-3, test-rackspace-win2022_vs2022-x64-3, test-azure_msft-win2022_vs2019-x64-4, test-azure_msft-win11_vs2022-arm64-4, test-softlayer-debian10-x64-1, test-digitalocean-fedora37-x64-1, test-digitalocean-ubuntu1804-x64-1, test-ibm-rhel8-s390x-1, test-azure_msft-win2016_vs2017-x64-4, test-rackspace-win2019_vs2019-x64-1, test-azure_msft-win2022_vs2019-x64-1, test-azure_msft-win11_vs2022-arm64-6, test-azure_msft-win11_vs2022-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/52956/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52957/
Example
not ok 655 parallel/test-runner-output
  ---
  duration_ms: 2778.98900
  severity: fail
  exitcode: 1
  stack: |-
    TAP version 13
    # Subtest: test runner output
        # Subtest: test-runner/output/abort.js
        ok 1 - test-runner/output/abort.js
          ---
          duration_ms: 1400.2546
          ...


Reason parallel/test-runner-watch-mode
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/48528/, https://github.com/nodejs/node/pull/48740/)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-8, test-osuosl-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/52961/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52963/
Example
not ok 2717 parallel/test-runner-watch-mode
  ---
  duration_ms: 120063.61500
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    TAP version 13
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-tmp/.tmp.2438/dependent.js
    Updating /home/iojs/node-t...

Reason parallel/test-tls-dhe
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/42387/, https://github.com/nodejs/node/pull/48607/)
Appeared test-rackspace-win2019_vs2019-x64-2, test-azure_msft-win2016_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/52904/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52959/
Example
not ok 735 parallel/test-tls-dhe
  ---
  duration_ms: 483.98700
  severity: fail
  exitcode: 1
  stack: |-
    node:events:492
          throw er; // Unhandled 'error' event
          ^
    
    Error: E41F0000:error:0A00041A:SSL routines:ssl3_read_bytes:tlsv1 alert decode error:C:\workspace\node-compile-windows\node\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1586:SSL alert number 50
    
    Emitted 'error' event on TLSSocket instance at:
        at TLSSocket._emitTLSError (node:_tls_wrap:994:10)
        at TLSWrap.onerror (node:_tls_wrap:482:11) {
      library: 'SSL routines',
      reason: 'tlsv1 alert decode error',
      code: 'ERR_SSL_TLSV1_ALERT_DECODE_ERROR'
    }
    
    Node.js v21.0.0-pre
  ...


Reason pummel/test-crypto-timing-safe-equal-benchmarks
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/48896/, https://github.com/nodejs/node/pull/48663/)
Appeared test-ibm-aix72-ppc64_be-2
First CI https://ci.nodejs.org/job/node-test-pull-request/52909/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52915/
Example
not ok 3588 pummel/test-crypto-timing-safe-equal-benchmarks
  ---
  duration_ms: 3275.33200
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: timingSafeEqual should not leak information from its execution time (t=6.27863503155761)
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix72-ppc64/test/pummel/test-crypto-timing-safe-equal-benchmarks.js:109:1)
        at Module._compile (node:internal/modules/cjs/loader:1233:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1287:10)
        at Module.load (node:internal/modules/cjs/loader:1091:32)
        at Module._load (node:internal/modules/cjs/loader:938:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47 {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='...

Reason pummel/test-heapdump-shadow-realm
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/48913/, https://github.com/nodejs/node/pull/48933/)
Appeared test-digitalocean-fedora38-x64-2, test-softlayer-debian10-x64-1, test-equinix_mnx-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/52957/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52966/
Example
not ok 3609 pummel/test-heapdump-shadow-realm
  ---
  duration_ms: 61602.40700
  severity: crashed
  exitcode: -6
  stack: |-
    
    <--- Last few GCs --->
    
    [3084753:0x5ff4140]    38393 ms: Scavenge (reduce) 975.2 (991.5) -> 974.9 (992.5) MB, 22.60 / 0.00 ms  (average mu = 0.293, current mu = 0.260) allocation failure; 
    [3084753:0x5ff4140]    39523 ms: Mark-Compact (reduce) 976.0 (993.0) -> 975.6 (993.2) MB, 917.06 / 0.00 ms  (+ 54.6 ms in 13 steps since start of marking, biggest step 10.9 ms, walltime since start of marking 981 ms) (average mu = 0.240, current mu = 0.17
    
    <--- JS stacktrace --->
    
    FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
     1: 0xc9a170 node::Abort() [out/Release/node]
     2: 0xb7d7ac  [out/Release/node]
     3: 0xee5410 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [out/Release/node]
     4: 0xee57cc v8::internal::V8::FatalProcessOutOfMemory(v8::internal::I...

Reason sequential/test-http-regr-gh-2928
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/48907/, https://github.com/nodejs/node/pull/48698/)
Appeared test-rackspace-win2012r2_vs2015-x64-1, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/52923/
Last CI https://ci.nodejs.org/job/node-test-pull-request/52991/
Example
not ok 922 sequential/test-http-regr-gh-2928
  ---
  duration_ms: 639.99700
  severity: fail
  exitcode: 3221226505
  stack: |-
    .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.
  ...


Git Failure
Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (7)
  • Build timed out (after 30 minutes). Marking the build as failed. (2)
  • fatal error: Killed signal terminated program cc1plus (5)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • parallel/test-fs-watch-recursive-add-file-to-existing-subfolder (5)
  • parallel/test-inspector-open-dispose (4)
  • sequential/test-perf-hooks (4)
  • wpt/test-structured-clone (4)
  • parallel/test-crypto-dh (3)
  • sequential/test-worker-prof (3)
  • node-api/test_threadsafe_function/test (2)
  • parallel/test-debugger-exceptions (2)
  • parallel/test-runner-output (2)
  • parallel/test-runner-watch-mode (2)
  • parallel/test-tls-dhe (2)
  • pummel/test-crypto-timing-safe-equal-benchmarks (2)
  • pummel/test-heapdump-shadow-realm (2)
  • sequential/test-http-regr-gh-2928 (2)
Dominant language
Shell
Stars
57
Forks
20
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/reliability

All issues in nodejs/reliability

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.