CI Reliability 2022-11-05
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing-qa
Research direction
Start with the generated ncu-ci walk report and the linked CI logs, then inspect the named tests: test/pummel/test-fs-largefile.js, test/pummel/test-fs-readfile-tostring-fail.js, test/parallel/test-fs-watch-recursive.js, test/parallel/test-corepack-yarn-install.js, and the other listed entry points. Completion would require identifying the causes of the recurring failures and verifying the affected CI jobs no longer reproduce them.
Written by the indexing model from the issue text.
Description
Failures in node-test-pull-request/47598 to node-test-pull-request/47684 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-11-05 00:15 | 14 | 11 | 14 | 8 | 53 | 14.10% |
JSTest Failure
| Reason | pummel/test-fs-largefile |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 6 (https://github.com/nodejs/node/pull/44226/, https://github.com/nodejs/node/pull/45269/, https://github.com/nodejs/node/pull/44412/, https://github.com/nodejs/node/pull/45273/, https://github.com/nodejs/node/pull/45286/, https://github.com/nodejs-private/node-private/pull/366/) |
| Appeared | test-nearform-macos10.15-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47613/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47664/ |
Example
not ok 3399 pummel/test-fs-largefile
---
duration_ms: 0.99
severity: fail
exitcode: 1
stack: |-
node:internal/fs/utils:347
throw err;
^
Error: ENOSPC: no space left on device, ftruncate
at Object.ftruncateSync (node:fs:1131:3)
at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/pummel/test-fs-largefile.js:37:4)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Module._load (node:internal/modules/cjs/loader:878:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:82:12)
at node:internal/main/run_main_module:23:47 {
errno: -28,
syscall: 'ftruncate',
code: 'ENOSPC'
}
Node.js v19.0.1
...
| Reason | node-api/test_fatal/test2 |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/44458/, https://github.com/nodejs/node/pull/45156/, https://github.com/nodejs-private/node-private/pull/365/) |
| Appeared | test-joyent-smartos20-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47601/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47654/ |
Example
not ok 3583 node-api/test_fatal/test2
---
duration_ms: 300.167
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-fs-watch-recursive |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/45254/, https://github.com/nodejs/node/pull/45286/, https://github.com/nodejs/node/pull/45289/) |
| Appeared | test-osuosl-rhel8-ppc64_le-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-joyent-smartos20-x64-3, test-digitalocean-alpine312_container-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47631/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47684/ |
Example
not ok 1482 parallel/test-fs-watch-recursive
---
duration_ms: 121.842
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | pummel/test-fs-readfile-tostring-fail |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/44226/, https://github.com/nodejs/node/pull/45286/, https://github.com/nodejs-private/node-private/pull/366/) |
| Appeared | test-nearform-macos10.15-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47613/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47664/ |
Example
not ok 3400 pummel/test-fs-readfile-tostring-fail
---
duration_ms: 0.127
severity: fail
exitcode: 7
stack: |-
/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/pummel/test-fs-readfile-tostring-fail.js:73
throw err;
^
AssertionError [ERR_ASSERTION]: ifError got unwanted exception: ENOSPC: no space left on device, write
at Object.callback (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/pummel/test-fs-readfile-tostring-fail.js:31:37)
at callback (node:internal/streams/writable:555:21)
at onwriteError (node:internal/streams/writable:418:3)
at onwrite (node:internal/streams/writable:460:7)
at node:internal/fs/streams:439:14
at FSReqCallback.wrapper [as oncomplete] (node:fs:946:5) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: [Error: ENOSPC: no space left on device, write] {
errno: -28,
code: 'ENOSPC',
syscall: 'write'
},
expected...
| Reason | parallel/test-corepack-yarn-install |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45272/, https://github.com/nodejs-private/node-private/pull/362/) |
| Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47626/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47633/ |
Example
not ok 591 parallel/test-corepack-yarn-install
---
duration_ms: 2.415
severity: fail
exitcode: 1
stack: |-
(node:30811) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Segmentation fault (core dumped)
assert.js:118
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: yarn install got error code 139
at handleExit (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-corepack-yarn-install.js:60:10)
at handleExit (/home/iojs/build/workspace/node-test-commit-linux-containered/test/common/index.js:380:15)
at ChildProcess.exithandler (child_process.js:390:5)
at ChildProcess.emit (events.js:400:28)
at maybeClose (internal/child_process.js:1088:16)
at Process.ChildProcess._handle.one...
| Reason | parallel/test-fs-promises-file-handle-readFile |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45286/, https://github.com/nodejs-private/node-private/pull/366/) |
| Appeared | test-nearform-macos10.15-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47638/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47664/ |
Example
not ok 743 parallel/test-fs-promises-file-handle-readFile
---
duration_ms: 0.100
severity: fail
exitcode: 1
stack: |-
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: ENOSPC: no space left on device, ftruncate] {
errno: -28,
code: 'ENOSPC',
syscall: 'ftruncate'
}
Node.js v19.0.1
...
| Reason | parallel/test-fs-readfile |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45286/, https://github.com/nodejs-private/node-private/pull/366/) |
| Appeared | test-nearform-macos10.15-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47638/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47664/ |
Example
not ok 791 parallel/test-fs-readfile
---
duration_ms: 0.163
severity: fail
exitcode: 1
stack: |-
node:internal/fs/utils:347
throw err;
^
Error: ENOSPC: no space left on device, ftruncate
at Object.ftruncateSync (node:fs:1131:3)
at Object.truncateSync (node:fs:1090:14)
at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-fs-readfile.js:61:6)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Module._load (node:internal/modules/cjs/loader:878:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:82:12)
at node:internal/main/run_main_module:23:47 {
errno: -28,
syscall: 'ftruncate',
code: 'ENOSPC'
}
Node.js v19.0.1
...
Example
not ok 2036 parallel/test-release-npm
---
duration_ms: 0.609
severity: fail
exitcode: 1
stack: |-
node:assert:124
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
0 !== 1
at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-release-npm.js:20:10)
at Module._compile (node:internal/modules/cjs/loader:1205:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1259:10)
at Module.load (node:internal/modules/cjs/loader:1068:32)
at Module._load (node:internal/modules/cjs/loader:909:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:82:12)
at node:internal/main/run_main_module:23:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 0,
expected: 1,
operator: 'strictEqual'
}
Node.js v20.0.0
...
Jenkins Failure
| Reason | Backing channel 'JNLP4-connect connection from ... is disconnected. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45139/, https://github.com/nodejs/node/pull/45254/) |
| Appeared | test-digitalocean-freebsd12-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47607/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47628/ |
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:41107' is disconnected.
at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
at jdk.proxy2/jdk.proxy2.$Proxy87.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1215)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1207)
Build Failure
Example
error: remote GitHub already exists.
> git fetch --prune --no-tags GitHub
> git fetch --prune --no-tags https://github.com/nodejs/build.git +refs/heads/main:refs/remotes/jenkins_tmp
| Reason | ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 3 (https://github.com/nodejs-private/node-private/pull/362/, https://github.com/nodejs-private/node-private/pull/365/, https://github.com/nodejs-private/node-private/pull/366/) |
| Appeared | test-azure_msft-win10_vs2019-x64-2, test-rackspace-win2012r2_vs2019-x64-5, test-azure_msft-win10_vs2019-x64-3, test-rackspace-win2012r2_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-4, test-rackspace-win2012r2_vs2013-x64-1, test-azure_msft-win10_vs2019-x64-1, test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-6, test-rackspace-win2012r2_vs2019-x64-3, test-rackspace-win2012r2_vs2019-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47633/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47664/ |
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/nodejs-private/node-private/pull/365/, https://github.com/nodejs-private/node-private/pull/366/) |
| Appeared | test-ibm-ubuntu1804-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47643/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47674/ |
Example
Failed to trigger node-test-commit
| Reason | Failed to trigger sub builds |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45288/, https://github.com/nodejs/node/pull/45286/) |
| Appeared | undefined |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47647/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47655/ |
Example
Failed to trigger sub builds
| Reason | error: ld returned 1 exit status |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs-private/node-private/pull/366/, https://github.com/nodejs/node/pull/45286/) |
| Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-8 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47675/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47676/ |
Example
error: ld returned 1 exit status
deps/openssl/openssl-cli.target.mk:293: recipe for target '/home/iojs/build/workspace/node-test-commit-linux-containered/out/Release/openssl-cli' failed
make[2]: *** [/home/iojs/build/workspace/node-test-commit-linux-containered/out/Release/openssl-cli] Error 1
make[2]: *** Waiting for unfinished jobs....
rm 736d921f6b1b990ce7212282398c5c71fcfd32a0.intermediate 79feaad4809862e5f5b05339774ae21a1fc30cef.intermediate
Makefile:134: recipe for target 'node' failed
| Reason | fatal error: ld terminated with signal 9 [Killed] |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs-private/node-private/pull/363/, https://github.com/nodejs/node/pull/45274/) |
| Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/47634/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/47635/ |
Example
fatal error: ld terminated with signal 9 [Killed]
Git Failure
Progress
-
pummel/test-fs-largefile(6) -
node-api/test_fatal/test2(3) -
parallel/test-fs-watch-recursive(3) -
pummel/test-fs-readfile-tostring-fail(3) -
parallel/test-corepack-yarn-install(2) -
parallel/test-fs-promises-file-handle-readFile(2) -
parallel/test-fs-readfile(2) -
parallel/test-release-npm(2) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
error: remote GitHub already exists.(6) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(3) -
Failed to trigger node-test-commit(2) -
Failed to trigger sub builds(2) -
error: ld returned 1 exit status(2) -
fatal error: ld terminated with signal 9 [Killed](2)
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/reliability
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/reliability#1666 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
nodejs/reliability#1665 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
nodejs/reliability#1664 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/reliability#1663 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/reliability#1662 ·
All issues in nodejs/reliability
Similar issues
-
out-of-date
Difficulty 1/5 Under an hour Newbie friendliness 82/100
CachyOS/CachyOS-PKGBUILDS#1894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
community-scripts/ProxmoxVE#17396 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mattpocock/skills#1099 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100