CI Reliability 2022-12-01
Nessuno ha ancora preso questa issue.
- Lingua principale
- Shell
- Stelle
- 57
- Fork
- 20
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Failures in node-test-pull-request/48155 to node-test-pull-request/48250 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-12-01 00:16 | 2 | 5 | 31 | 5 | 57 | 5.38% |
JSTest Failure
Example
not ok 1056 parallel/test-fs-watch-recursive
---
duration_ms: 6.19
severity: fail
exitcode: 1
stack: |-
(node:498) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert(!process._getActiveHandles().some((handle) => handle.constructor.name === 'StatWatcher'))
at FSWatcher.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-fs-watch-recursive.js:264:5) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: '=='
}
Node.js v20.0.0-pre
...
Example
not ok 2463 parallel/test-process-wrap
---
duration_ms: 120.53
severity: fail
exitcode: -15
stack: |-
timeout
(node:67128) 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)
...
| Reason | parallel/test-child-process-stdio-inherit |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 5 (https://github.com/nodejs/node/pull/45590/, https://github.com/nodejs/node/pull/45615/, https://github.com/nodejs/node/pull/45501/, https://github.com/nodejs/node/pull/45500/, https://github.com/nodejs/node/pull/45526/) |
| Appeared | test-nearform-macos10.15-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48185/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48249/ |
Example
not ok 728 parallel/test-child-process-stdio-inherit
---
duration_ms: 120.107
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-child-process-exec-timeout-kill |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/45610/, https://github.com/nodejs/node/pull/45587/, https://github.com/nodejs/node/pull/45621/) |
| Appeared | test-digitalocean-freebsd12-x64-2, test-ibm-rhel8-s390x-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48161/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48197/ |
Example
not ok 365 parallel/test-child-process-exec-timeout-kill
---
duration_ms: 0.343
severity: fail
exitcode: 1
stack: |-
[stdout]
[stderr]
node:assert:124
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
1 !== null
at /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/parallel/test-child-process-exec-timeout-kill.js:32:10
at /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/common/index.js:448:15
at ChildProcess.exithandler (node:child_process:427:5)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1098:16)
at Socket.<anonymous> (node:internal/child_process:456:11)
at Socket.emit (node:events:519:28)
at Pipe.<anonymous> (node:net:298:12) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 1,
expected: null,
op...
| Reason | addons/report-fatalerror/test |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45634/, https://github.com/nodejs/node/pull/45676/) |
| Appeared | test-joyent-smartos20-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48212/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48233/ |
Example
not ok 3501 addons/report-fatalerror/test
---
duration_ms: 300.157
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-runner-exit-code |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45613/, https://github.com/nodejs/node/pull/45660/) |
| Appeared | test-nearform-macos10.15-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48163/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48226/ |
Example
not ok 2081 parallel/test-runner-exit-code
---
duration_ms: 0.534
severity: fail
exitcode: 1
stack: |-
node:internal/errors:478
ErrorCaptureStackTrace(err);
^
Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
at new NodeError (node:internal/errors:387:5)
at Socket.onclose (node:internal/streams/end-of-stream:145:30)
at Socket.emit (node:events:525:35)
at Pipe.<anonymous> (node:net:301:12) {
code: 'ERR_STREAM_PREMATURE_CLOSE'
}
...
| Reason | sequential/test-watch-mode |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/44873/, https://github.com/nodejs/node/pull/45660/) |
| Appeared | test-requireio_securogroup-debian10-arm64_pi3-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48214/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48226/ |
Example
not ok 886 sequential/test-watch-mode
---
duration_ms: 13.500
severity: fail
exitcode: 1
stack: |-
TAP version 13
# Subtest: watch mode
# Subtest: should watch changes to a file - event loop ended
ok 1 - should watch changes to a file - event loop ended
---
duration_ms: 7.259099031
...
Jenkins Failure
| Reason | Build timed out (after 60 minutes). Marking the build as failed. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/45583/, https://github.com/nodejs/node/pull/45595/, https://github.com/nodejs/node/pull/45633/, https://github.com/nodejs/node/pull/45672/) |
| Appeared | test-softlayer-ubi81_container-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48160/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48246/ |
Example
Build timed out (after 60 minutes). Marking the build as failed.
Git Failure
Build Failure
| Reason | error: remote GitHub already exists. |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/45587/, https://github.com/nodejs/node/pull/45615/, https://github.com/nodejs/node/pull/45653/, https://github.com/nodejs/node/pull/45597/) |
| Appeared | test-rackspace-win2012r2_vs2017-x64-1, test-rackspace-win2012r2_vs2019-x64-3, test-rackspace-win2012r2_vs2019-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48165/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48220/ |
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 | fatal error: ld terminated with signal 9 [Killed] |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45613/, https://github.com/nodejs/node/pull/45590/) |
| Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48168/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48170/ |
Example
fatal error: ld terminated with signal 9 [Killed]
CCTest Failure
Progress
-
parallel/test-fs-watch-recursive(13) -
parallel/test-process-wrap(9) -
parallel/test-child-process-stdio-inherit(5) -
parallel/test-child-process-exec-timeout-kill(3) -
addons/report-fatalerror/test(2) -
parallel/test-runner-exit-code(2) -
sequential/test-watch-mode(2) -
Build timed out (after 60 minutes). Marking the build as failed.(4) -
error: remote GitHub already exists.(4) -
fatal error: ld terminated with signal 9 [Killed](2)
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia dai test falliti elencati, in particolare test/parallel/test-fs-watch-recursive.js e test/parallel/test-process-wrap, quindi confronta i relativi log Jenkins collegati sulle piattaforme segnalate. Esamina gli altri percorsi dei test e le esecuzioni CI menzionati per identificare cause riproducibili; il lavoro è completato quando i fallimenti ricorrenti sono stati risolti e i job CI interessati non falliscono più per questi motivi.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- javascript, node.js, shell
- Ambito
- ci-cd, devops, testing-qa
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100