CI Reliability 2022-12-18
Offen
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Shell
- Sterne
- 57
- Forks
- 20
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Failures in node-test-pull-request/48450 to node-test-pull-request/48543 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-18 00:12 | 4 | 4 | 15 | 16 | 61 | 5.00% |
CCTest Failure
Jenkins Failure
| Reason | Backing channel 'JNLP4-connect connection from ... is disconnected. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/45849/, https://github.com/nodejs/node/pull/45852/, https://github.com/nodejs/node/pull/45871/, https://github.com/nodejs/node/pull/45870/) |
| Appeared | test-nearform_arm-win10_vs2019-arm64-2, test-osuosl-ubuntu2004_container-armv7l-1, test-orka-macos11-x64-1, test-digitalocean-freebsd12-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48458/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48518/ |
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from ip-83-147-191-74.broadband.digiweb.ie/83.147.191.74:57121' is disconnected.
at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
at jdk.proxy2/jdk.proxy2.$Proxy82.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 60 minutes). Marking the build as failed. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/44943/, https://github.com/nodejs/node/pull/45869/, https://github.com/nodejs/node/pull/45857/) |
| Appeared | test-rackspace-win2012r2_vs2019-x64-3, test-softlayer-ubi81_container-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48494/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48534/ |
Example
Build timed out (after 60 minutes). Marking the build as failed.
Git Failure
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:1003)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1244)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1308)
at hudson.scm.SCM.checkout(SCM.java:540)
Build Failure
Example
Error: getWindowSize EINVAL
outline = at WriteStream._refreshSize (tty.js:133:31)
outline = at process.<anonymous> (internal/bootstrap/switches/is_main_thread.js:127:41)
outline = at process.emit (events.js:400:28)
outline = Emitted 'error' event on WriteStream instance at:
outline = at WriteStream._refreshSize (tty.js:133:10)
| Reason | error: remote GitHub already exists. |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/45849/, https://github.com/nodejs/node/pull/45878/, https://github.com/nodejs/node/pull/45882/) |
| Appeared | test-rackspace-win2012r2_vs2019-x64-1, test-rackspace-win2012r2_vs2017-x64-1, test-rackspace-win2012r2_vs2019-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48483/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48514/ |
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 workspace for ... |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45871/, https://github.com/nodejs/node/pull/45803/) |
| Appeared | test-joyent-smartos20-x64-3, test-osuosl-aix72-ppc64_be-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48510/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48528/ |
Example
ERROR: Step ?Publish JUnit test result report? failed: no workspace for node-test-commit-smartos/nodes=smartos20-64 #47077
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
| Reason | ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45870/, https://github.com/nodejs/node/pull/45608/) |
| Appeared | test-nearform-macos11.0-arm64-1, test-nearform-macos10.15-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48518/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48519/ |
Example
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-osx-arm/nodes=osx11 #9023
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
| Reason | Failed to trigger sub builds |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45869/, https://github.com/nodejs/node/pull/45865/) |
| Appeared | undefined |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48516/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48532/ |
Example
Failed to trigger sub builds
undefined
JSTest Failure
Example
not ok 1231 parallel/test-fs-watch-recursive
---
duration_ms: 120.118
severity: fail
exitcode: -15
stack: |-
timeout
(node:19567) 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)
...
Example
not ok 3468 pummel/test-net-throttle
---
duration_ms: 0.586
severity: fail
exitcode: 1
stack: |-
node:assert:124
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
false !== true
at process.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/pummel/test-net-throttle.js:87:10)
at process.emit (node:events:531:35) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: 'strictEqual'
}
Node.js v20.0.0-pre
...
| Reason | parallel/test-watch-mode-files_watcher |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/45778/, https://github.com/nodejs/node/pull/45750/, https://github.com/nodejs/node/pull/45857/) |
| Appeared | test-softlayer-ubuntu1804_sharedlibs_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-7, test-orka-macos11-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48471/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48534/ |
Example
not ok 3090 parallel/test-watch-mode-files_watcher
---
duration_ms: 2.25
severity: fail
exitcode: 1
stack: |-
TAP version 13
# Subtest: watch mode file watcher
# Subtest: should watch changed files
not ok 1 - should watch changed files
---
duration_ms: 3.989003
failureType: 'testCodeFailure'
error: "ENOSPC: System limit for number of file watchers reached, watch '/home/iojs/node-tmp/.tmp.3074/file1'"
code: 'ENOSPC'
stack: |-
FSWatcher.<computed> (node:internal/fs/watchers:244:19)
watch (node:fs:2304:36)
FilesWatcher.watchPath (node:internal/watch_mode/files_watcher:92:21)
FilesWatcher.filterFile (node:internal/watch_mode/files_watcher:108:12)
Object.<anonymous> (file:///home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-watch-mode-files_watcher.mjs:49:13)
ItTest.runInAsyncScope (node:async_hooks:204:9)
ItT...
| Reason | parallel/test-tls-ticket-cluster |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45851/, https://github.com/nodejs/node/pull/44943/) |
| Appeared | test-azure_msft-win10_vs2019-x64-4, test-nearform_arm-win10_vs2019-arm64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48460/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48508/ |
Example
not ok 729 parallel/test-tls-ticket-cluster
---
duration_ms: 0.723
severity: fail
exitcode: 1
stack: |-
[primary] got "listening"
[primary] connecting 59851 session? false
[primary] got "listening"
[primary] got "listening"
[primary] connecting 59851 session? false
[worker] connection reused? false
[primary] got "not-reused"
[primary] connecting 59851 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59851 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59851 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59851 session? true
[primary] got "listening"
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59851 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59851 session? true
[worker] connection reused? true
...
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(4) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
ERROR: Error fetching remote repo 'origin'(26) -
Error: getWindowSize EINVAL(13) -
error: remote GitHub already exists.(3) -
ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...(2) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
Failed to trigger sub builds(2) -
parallel/test-fs-watch-recursive(9) -
pummel/test-net-throttle(7) -
parallel/test-watch-mode-files_watcher(3) -
parallel/test-tls-ticket-cluster(2)
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit den verlinkten node-test-pull-request-Jobs und Beispiel-Jenkins-Logs und gruppiere die gemeldeten Jenkins-, Git-, Build- und JavaScript-Testfehler nach Ursache und betroffenem Worker. Erledigt ist die Aufgabe, wenn jeder wiederkehrende Fehler eine identifizierte Ursache und eine nachverfolgte Behebung hat oder als vorübergehend bestätigt wurde.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- git, node.js, shell
- Bereich
- ci-cd, devops, infrastructure, testing-qa
- Issue-Typ
- Bug
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 20/100