CI Reliability 2022-01-12

Open
#171 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
18/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js, shell
Domain
ci-cd, testing-qa

Research direction

Start by reading the linked CI logs and reproducing the named failures, including test/parallel/test-fs-rmdir-recursive, test/sequential/test-performance-eventloopdelay.js, and the crypto and child-process tests. The issue covers several platforms and test suites; done would require isolating and addressing the reported reliability failures so the affected CI runs no longer fail intermittently.

Written by the indexing model from the issue text.

Description

Failures in node-test-pull-request/41726 to node-test-pull-request/41825 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-01-12 00:02 0 5 24 3 68 5.15%
JSTest Failure
Reason parallel/test-fs-rmdir-recursive
Type JS_TEST_FAILURE
Failed PR 17 (https://github.com/nodejs/node/pull/41290/, https://github.com/nodejs/node/pull/41263/, https://github.com/nodejs/node/pull/41403/, https://github.com/nodejs/node/pull/41352/, https://github.com/nodejs/node/pull/41421/, https://github.com/nodejs/node/pull/41388/, https://github.com/nodejs/node/pull/41441/, https://github.com/nodejs/node/pull/41425/, https://github.com/nodejs/node/pull/41406/, https://github.com/nodejs/node/pull/41445/, https://github.com/nodejs-private/node-private/pull/300/, https://github.com/nodejs-private/node-private/pull/305/, https://github.com/nodejs/node/pull/41197/, https://github.com/nodejs/node/pull/41457/, https://github.com/nodejs/node/pull/41329/, https://github.com/nodejs/node/pull/41451/, https://github.com/nodejs/node/pull/41478/)
Appeared test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vcbt2015-x64-1, test-azure_msft-win10_vcbt2015-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/41747/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41821/
Example
not ok 259 parallel/test-fs-rmdir-recursive
  ---
  duration_ms: 0.735
  severity: fail
  exitcode: 1
  stack: |-
    (node:11136) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
    (Use `node --trace-deprecation ...` to show where the warning was created)
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256
    Files blocking: [ 'rmdir-recursive-0', 'rmdir-recursive-4', 'rmdir-recursive-5' ]
    
    node:assert:991
        throw newErr;
        ^
    
    AssertionError [ERR_ASSERTION]: ifError got unwanted exception: ENOTEMPTY: directory not empty, rmdir 'C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256\rmdir-recursive-0\d-3-1\d-2-1'
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:364:12
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:401:15
        at node:fs:188:23
 ...

Reason sequential/test-performance-eventloopdelay
Type JS_TEST_FAILURE
Failed PR 13 (https://github.com/nodejs/node/pull/41197/, https://github.com/nodejs/node/pull/41325/, https://github.com/nodejs/node/pull/41397/, https://github.com/nodejs/node/pull/41398/, https://github.com/nodejs/node/pull/41302/, https://github.com/nodejs/node/pull/41385/, https://github.com/nodejs/node/pull/41329/, https://github.com/nodejs/node/pull/41290/, https://github.com/nodejs/node/pull/41369/, https://github.com/nodejs/node/pull/41263/, https://github.com/nodejs/node/pull/38590/, https://github.com/nodejs/node/pull/41352/, https://github.com/nodejs-private/node-private/pull/307/)
Appeared test-ibm-rhel7-s390x-1, test-ibm-rhel7-s390x-3, test-ibm-rhel7-s390x-2, test-ibm-rhel7-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/41732/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41797/
Example
not ok 3530 sequential/test-performance-eventloopdelay
  ---
  duration_ms: 7.219
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
    
      assert(histogram.min > 0)
    
        at Timeout.spinAWhile [as _onTimeout] (/home/iojs/build/workspace/node-test-commit-linuxone/test/sequential/test-performance-eventloopdelay.js:65:7)
        at listOnTimeout (node:internal/timers:568:17)
        at processTimers (node:internal/timers:510:7) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v18.0.0-pre
  ...


Reason parallel/test-common-expect-warning
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/41403/, https://github.com/nodejs/node/pull/41263/, https://github.com/nodejs/node/pull/40661/, https://github.com/nodejs-private/node-private/pull/300/, https://github.com/nodejs/node/pull/41329/)
Appeared test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41753/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41819/
Example
not ok 320 parallel/test-common-expect-warning
  ---
  duration_ms: 0.521
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:1026
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The input did not match the regular expression /Unexpected extra warning received/. Input:
    
    ''
    
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/parallel/test-common-expect-warning.js:41:14)
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/common/index.js:401:15)
        at ChildProcess.emit (node:events:520:28)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '',
      expected: /Unexpected extra warning received/,
      operator: 'match'
    }
    
    Node.js v18.0.0-pre
  ...


Reason parallel/test-child-process-pipe-dataflow
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/41409/, https://github.com/nodejs/node/pull/41197/, https://github.com/nodejs/node/pull/41457/)
Appeared test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/41766/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41818/
Example
not ok 81 parallel/test-child-process-pipe-dataflow
  ---
  duration_ms: 1.73
  severity: fail
  exitcode: 1
  stack: |-
    assert.js:101
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    '0' !== '1048577'
    
        at Socket.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-pipe-dataflow.js:66:12)
        at Socket.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:361:15)
        at Socket.emit (events.js:314:20)
        at addChunk (_stream_readable.js:297:12)
        at readableAddChunk (_stream_readable.js:272:9)
        at Socket.Readable.push (_stream_readable.js:213:10)
        at Pipe.onStreamRead (internal/stream_base_commons.js:188:23) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '0',
      expected: '1048577',
      operator: 'strictEqual'
    }
  ...


Reason parallel/test-crypto-classes
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/41325/, https://github.com/nodejs/node/pull/41352/, https://github.com/nodejs/node/pull/38590/)
Appeared test-requireio_joeyvandijk-debian10-armv7l_pi2-2, test-requireio_svincent-debian10-armv7l_pi2-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41742/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41770/
Example
not ok 194 parallel/test-crypto-classes
  ---
  duration_ms: 240.160
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-dh-odd-key
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/41385/, https://github.com/nodejs/node/pull/41409/, https://github.com/nodejs/node/pull/41197/)
Appeared test-requireio_joeyvandijk-debian10-armv7l_pi2-2, test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_securogroup-debian10-arm64_pi3-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41743/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41816/
Example
not ok 239 parallel/test-crypto-dh-odd-key
  ---
  duration_ms: 240.136
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason node-api/test_threadsafe_function/test
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/40661/, https://github.com/nodejs/node/pull/38590/)
Appeared test-equinix-centos7_container-arm64-1, test-equinix-ubuntu2004_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41761/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41770/
Example
not ok 3341 node-api/test_threadsafe_function/test
  ---
  duration_ms: 240.82
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-binary-default
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41329/, https://github.com/nodejs/node/pull/41445/)
Appeared test-requireio_jasnell-debian10-armv7l_pi2-1, test-requireio_svincent-debian10-armv7l_pi2-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41791/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41795/
Example
not ok 159 parallel/test-crypto-binary-default
  ---
  duration_ms: 240.90
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-fs-rm
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41329/, https://github.com/nodejs-private/node-private/pull/310/)
Appeared test-azure_msft-win10_vcbt2015-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/41791/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41805/
Example
not ok 237 parallel/test-fs-rm
  ---
  duration_ms: 0.536
  severity: fail
  exitcode: 1
  stack: |-
    assert.js:630
          throw err;
          ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
    + actual - expected
    
      Comparison {
    +   syscall: 'rm'
    -   syscall: 'stat'
      }
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-fs-rm.js:161:10)
        at Module._compile (internal/modules/cjs/loader.js:1085:14)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
        at Module.load (internal/modules/cjs/loader.js:950:32)
        at Function.Module._load (internal/modules/cjs/loader.js:790:12)
        at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
        at internal/main/run_main_module.js:17:47 {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: SystemError [ERR_FS_EISDIR]: Path is a directory: rm returned E...

Reason parallel/test-tls-ticket-cluster
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs-private/node-private/pull/309/, https://github.com/nodejs-private/node-private/pull/308/)
Appeared test-nearform-macos10.15-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/41803/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41811/
Example
not ok 2151 parallel/test-tls-ticket-cluster
  ---
  duration_ms: 0.374
  severity: fail
  exitcode: 1
  stack: |-
    [master] got "listening"
    [master] connecting 61737 session? false
    [worker] connection reused? false
    [master] got "not-reused"
    [master] connecting 61737 session? true
    [worker] connection reused? true
    [master] got "reused"
    [master] connecting 61737 session? true
    [worker] connection reused? true
    [master] got "reused"
    [master] connecting 61737 session? true
    [worker] connection reused? true
    [master] got "reused"
    [master] connecting 61737 session? true
    [worker] connection reused? true
    [master] got "reused"
    [master] connecting 61737 session? true
    [worker] connection reused? true
    [master] got "reused"
    [master] connecting 61737 session? true
    [worker] connection reused? true
    [master] got "reused"
    [master] connecting 61737 session? true
    [worker] connection reused? true
    [master] got "reused"
    [master] conne...

Reason parallel/test-trace-events-fs-sync
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41369/, https://github.com/nodejs/node/pull/41388/)
Appeared test-azure_msft-win10_vcbt2015-x64-4, test-azure_msft-win10_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/41734/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41779/
Example
not ok 692 parallel/test-trace-events-fs-sync
  ---
  duration_ms: 2.954
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-trace-events-fs-sync.js:133
        throw new Error(`${tr}:\n${util.inspect(proc)}`);
        ^
    
    Error: fs.sync.fstat:
    {
      status: 1,
      signal: null,
      output: [
        null,
        '',
        'node:internal/fs/utils:344\r\n' +
          '    throw err;\r\n' +
          '    ^\r\n' +
          '\r\n' +
          "Error: EPERM: operation not permitted, open 'fs.txt'\r\n" +
          '    at Object.openSync (node:fs:585:3)\r\n' +
          '    at Object.writeFileSync (node:fs:2155:35)\r\n' +
          '    at [eval]:1:4\r\n' +
          '    at Script.runInThisContext (node:vm:129:12)\r\n' +
          '    at Object.runInThisContext (node:vm:305:38)\r\n' +
          '    at node:internal/process/execution:75:19\r\n' +
          '    at [eval]-wrapper:6:22\r\n' +
          '    at evalScript (nod...

Reason pummel/test-worker-take-heapsnapshot
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs-private/node-private/pull/307/, https://github.com/nodejs-private/node-private/pull/300/)
Appeared test-equinix-ubuntu1804_sharedlibs_container-arm64-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/41797/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41798/
Example
not ok 3237 pummel/test-worker-take-heapsnapshot
  ---
  duration_ms: 0.614
  severity: crashed
  exitcode: -11
  stack: |-
    (node:1938508) internal/test/binding: These APIs are for internal testing only. Do not use them.
    (Use `node --trace-warnings ...` to show where the warning was created)
  ...


Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/41424/, https://github.com/nodejs/node/pull/41451/, https://github.com/nodejs-private/node-private/pull/300/, https://github.com/nodejs/node/pull/41478/, https://github.com/nodejs/node/pull/41479/)
Appeared test-macstadium-macos11.0-arm64-3, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-centos7_container-arm64-2, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41790/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41822/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 207.254.38.86/207.254.38.86:61290' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
	at com.sun.proxy.$Proxy82.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)

Git Failure
Reason ERROR: Error fetching remote repo 'origin'
Type GIT_FAILURE
Failed PR 10 (https://github.com/nodejs/node/pull/41352/, https://github.com/nodejs/node/pull/41373/, https://github.com/nodejs/node/pull/41197/, https://github.com/nodejs/node/pull/41369/, https://github.com/nodejs/node/pull/41325/, https://github.com/nodejs/node/pull/41397/, https://github.com/nodejs/node/pull/41329/, https://github.com/nodejs/node/pull/41445/, https://github.com/nodejs/node/pull/41451/, https://github.com/nodejs-private/node-private/pull/300/)
Appeared test-equinix-centos7_container-arm64-2, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2, test-ibm-ubuntu1804-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41728/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41801/
Example
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from git@github.com:nodejs/node.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1001)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1242)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1302)
	at hudson.scm.SCM.checkout(SCM.java:505)

Reason Error: git whatchanged --no-abbrev -M "--format=commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(0,4,4)%B" -n 1024 f1658bdc8f84950b4fab9e8a4e1561fd05a043df ^origin/_jenkins_local_branch~1 in /home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64
Type GIT_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/41352/, https://github.com/nodejs/node/pull/41197/, https://github.com/nodejs/node/pull/41369/, https://github.com/nodejs/node/pull/41325/, https://github.com/nodejs/node/pull/41397/)
Appeared test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41728/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41736/
Example
hudson.plugins.git.GitException: Error: git whatchanged --no-abbrev -M "--format=commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(0,4,4)%B" -n 1024 f1658bdc8f84950b4fab9e8a4e1561fd05a043df ^origin/_jenkins_local_branch~1 in /home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$6.execute(CliGitAPIImpl.java:1272)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:160)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:153)
	at hudson.remoting.UserRequest.perform(UserRequest.java:211)

Build Failure
Reason Failed to trigger fanned build
Type BUILD_FAILURE
Failed PR 7 (https://github.com/nodejs/node/pull/41352/, https://github.com/nodejs/node/pull/41373/, https://github.com/nodejs/node/pull/41197/, https://github.com/nodejs/node/pull/41367/, https://github.com/nodejs/node/pull/41369/, https://github.com/nodejs/node/pull/41325/, https://github.com/nodejs/node/pull/41397/)
Appeared undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/41728/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41736/
Example
Failed to trigger fanned build

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/41325/, https://github.com/nodejs/node/pull/41388/)
Appeared test-requireio_mcollina-debian10-armv7l_pi2-1, test-requireio_davglass-debian10-arm64_pi3-1, test-requireio_svincent-debian10-armv7l_pi2-3, test-requireio_securogroup-debian10-arm64_pi3-1, test-requireio_jasnell-debian10-armv7l_pi2-1, test-requireio_williamkapke-debian10-arm64_pi3-2, test-requireio_piccoloaiutante-debian10-arm64_pi3-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-1, test-requireio_williamkapke-debian10-arm64_pi3-1, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41742/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41781/
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-arm] $ /bin/bash -ex /tmp/jenkins3143989216785633656.sh
+ '[' -d .git ']'
+ git clean -fdx

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/41388/, https://github.com/nodejs-private/node-private/pull/300/)
Appeared test-azure_msft-win10_vcbt2015-x64-2, test-azure_msft-win10_vs2019-x64-2, test-rackspace-win2012r2_vs2015-x64-1, test-rackspace-win2012r2_vs2019-x64-5, test-azure_msft-win10_vcbt2015-x64-1, test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41781/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41799/
Example
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason Failed to trigger node-test-commit
Type BUILD_FAILURE
Failed PR 2 (https://github.com/node/node/pull/41197/, https://github.com/nodejs-private/node-private/pull/309/)
Appeared test-packetnet-ubuntu1804-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41731/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41802/
Example
Failed to trigger node-test-commit

undefined
Reason Unknown
Type undefined
Failed PR 18 (https://github.com/nodejs/node/pull/41302/, https://github.com/nodejs/node/pull/41325/, https://github.com/nodejs/node/pull/41385/, https://github.com/nodejs/node/pull/41403/, https://github.com/nodejs/node/pull/41263/, https://github.com/nodejs/node/pull/41409/, https://github.com/nodejs/node/pull/41352/, https://github.com/nodejs/node/pull/38590/, https://github.com/nodejs/node/pull/41414/, https://github.com/nodejs/node/pull/41421/, https://github.com/nodejs/node/pull/41388/, https://github.com/nodejs/node/pull/41329/, https://github.com/nodejs/node/pull/41445/, https://github.com/nodejs/node/pull/41451/, https://github.com/nodejs-private/node-private/pull/307/, https://github.com/nodejs-private/node-private/pull/300/, https://github.com/nodejs-private/node-private/pull/310/, https://github.com/nodejs/node/pull/41197/)
Appeared test-equinix-ubuntu2004_container-armv7l-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/41738/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41816/
Example
Unknown

Progress
  • parallel/test-fs-rmdir-recursive (17)
  • sequential/test-performance-eventloopdelay (13)
  • parallel/test-common-expect-warning (5)
  • parallel/test-child-process-pipe-dataflow (3)
  • parallel/test-crypto-classes (3)
  • parallel/test-crypto-dh-odd-key (3)
  • node-api/test_threadsafe_function/test (2)
  • parallel/test-crypto-binary-default (2)
  • parallel/test-fs-rm (2)
  • parallel/test-tls-ticket-cluster (2)
  • parallel/test-trace-events-fs-sync (2)
  • pummel/test-worker-take-heapsnapshot (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (5)
  • ERROR: Error fetching remote repo 'origin' (10)
  • Error: git whatchanged --no-abbrev -M "--format=commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(0,4,4)%B" -n 1024 f1658bdc8f84950b4fab9e8a4e1561fd05a043df ^origin/_jenkins_local_branch~1 in /home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64 (5)
  • Failed to trigger fanned build (7)
  • 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 test report files were found. Configuration error? (2)
  • Failed to trigger node-test-commit (2)
  • Unknown (18)
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.