nodejs / nodejs/reliability

CI Reliability 2022-12-18

Aperta
#461 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

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/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
Reason ERROR: Error fetching remote repo 'origin'
Type GIT_FAILURE
Failed PR 26 (https://github.com/nodejs/node/pull/45778/, https://github.com/nodejs/node/pull/45856/, https://github.com/nodejs/node/pull/45852/, https://github.com/nodejs/node/pull/45867/, https://github.com/nodejs/node/pull/45851/, https://github.com/nodejs/node/pull/45596/, https://github.com/nodejs/node/pull/45860/, https://github.com/nodejs/node/pull/45855/, https://github.com/nodejs/node/pull/45854/, https://github.com/nodejs/node/pull/45865/, https://github.com/nodejs/node/pull/45803/, https://github.com/nodejs/node/pull/45869/, https://github.com/nodejs/node/pull/44943/, https://github.com/nodejs/node/pull/45849/, https://github.com/nodejs/node/pull/45871/, https://github.com/nodejs/node/pull/45878/, https://github.com/nodejs/node/pull/45621/, https://github.com/nodejs/node/pull/45870/, https://github.com/nodejs/node/pull/45608/, https://github.com/nodejs/node/pull/44445/, https://github.com/nodejs/node/pull/45882/, https://github.com/nodejs/node/pull/45887/, https://github.com/nodejs/node/pull/45886/, https://github.com/nodejs/node/pull/45885/, https://github.com/nodejs/node/pull/45877/, https://github.com/nodejs/node/pull/45894/)
Appeared test-orka-macos10.15-x64-2, test-orka-macos11-x64-2, test-orka-macos11-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48480/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48543/
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
Reason Error: getWindowSize EINVAL
Type BUILD_FAILURE
Failed PR 13 (https://github.com/nodejs/node/pull/45704/, https://github.com/nodejs/node/pull/45831/, https://github.com/nodejs/node/pull/45855/, https://github.com/nodejs/node/pull/45850/, https://github.com/nodejs/node/pull/45750/, https://github.com/nodejs/node/pull/45856/, https://github.com/nodejs/node/pull/45849/, https://github.com/nodejs/node/pull/44943/, https://github.com/nodejs/node/pull/45621/, https://github.com/nodejs/node/pull/45803/, https://github.com/nodejs/node/pull/45608/, https://github.com/nodejs/node/pull/45877/, https://github.com/nodejs/node/pull/45894/)
Appeared test-equinix_mnx-smartos18-x64-3, test-equinix_mnx-smartos20-x64-4, test-equinix_mnx-smartos20-x64-3, test-joyent-smartos18-x64-3, test-joyent-smartos20-x64-4, test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/48450/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48543/
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
Reason parallel/test-fs-watch-recursive
Type JS_TEST_FAILURE
Failed PR 9 (https://github.com/nodejs/node/pull/45604/, https://github.com/nodejs/node/pull/45778/, https://github.com/nodejs/node/pull/45777/, https://github.com/nodejs/node/pull/45856/, https://github.com/nodejs/node/pull/45849/, https://github.com/nodejs/node/pull/45869/, https://github.com/nodejs/node/pull/45886/, https://github.com/nodejs/node/pull/43772/, https://github.com/nodejs/node/pull/44445/)
Appeared test-orka-macos11-x64-2, test-softlayer-alpine311_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-equinix-rhel8_container-arm64-2, test-nearform-macos10.15-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-8, test-orka-macos11-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-1, test-nearform-macos11.0-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48464/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48541/
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)
  ...


Reason pummel/test-net-throttle
Type JS_TEST_FAILURE
Failed PR 7 (https://github.com/nodejs/node/pull/45831/, https://github.com/nodejs/node/pull/45851/, https://github.com/nodejs/node/pull/45852/, https://github.com/nodejs/node/pull/45867/, https://github.com/nodejs/node/pull/45886/, https://github.com/nodejs/node/pull/45885/, https://github.com/nodejs/node/pull/45857/)
Appeared test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/48452/
Last CI https://ci.nodejs.org/job/node-test-pull-request/48534/
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)

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia dai job node-test-pull-request collegati e dai log Jenkins di esempio, raggruppando gli errori segnalati di Jenkins, Git, build e test JavaScript per causa e worker interessato. Il lavoro è completato quando ogni errore ricorrente ha una causa identificata e una remediation tracciata, oppure è stato confermato come transitorio.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
git, node.js, shell
Ambito
ci-cd, devops, infrastructure, testing-qa
Tipo di issue
Bug
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
20/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.