CI Reliability 2022-10-28

Ouverte
#413 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
20/100
Type d'issue
Bug
Clarté
À clarifier
Activité
À l'abandon
Stack technique
node.js, shell
Domaine
ci-cd, testing-qa

Piste de recherche

Commencez par les exemples de CI liés et les échecs mentionnés dans test/pummel, test/parallel, addons/request-interrupt/test et node-api/test_fatal/test2. Comparez les logs enregistrés sur les plateformes concernées et examinez séparément les échecs de Jenkins. La tâche est terminée lorsque les échecs récurrents de CI signalés ont une cause identifiée et corrigée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Failures in node-test-pull-request/47414 to node-test-pull-request/47511 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-10-28 00:17 3 6 35 4 52 6.45%
JSTest Failure
Reason pummel/test-fs-readfile-tostring-fail
Type JS_TEST_FAILURE
Failed PR 8 (https://github.com/nodejs/node/pull/45129/, https://github.com/nodejs/node/pull/45092/, https://github.com/nodejs/node/pull/44713/, https://github.com/nodejs/node/pull/45098/, https://github.com/nodejs/node/pull/45135/, https://github.com/nodejs/node/pull/45132/, https://github.com/nodejs/node/pull/45133/, https://github.com/nodejs/node/pull/45043/)
Appeared test-orka-macos11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47417/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47439/
Example
not ok 3409 pummel/test-fs-readfile-tostring-fail
  ---
  duration_ms: 0.344
  severity: fail
  exitcode: 7
  stack: |-
    /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/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/osx11-x64/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'
      },
      expe...

Reason parallel/test-watch-mode-files_watcher
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/45095/, https://github.com/nodejs/node/pull/45153/, https://github.com/nodejs/node/pull/45165/, https://github.com/nodejs/node/pull/45091/)
Appeared test-softlayer-ubi81_container-x64-1, test-orka-macos11-x64-2, test-equinix-debian10_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47414/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47497/
Example
not ok 3066 parallel/test-watch-mode-files_watcher
  ---
  duration_ms: 1.850
  severity: fail
  exitcode: 1
  stack: |-
    TAP version 13
    # Subtest: watch mode file watcher
        # Subtest: should watch changed files
        ok 1 - should watch changed files
          ---
          duration_ms: 107.513444
          ...


Reason pummel/test-fs-largefile
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/45135/, https://github.com/nodejs/node/pull/44935/, https://github.com/nodejs/node/pull/45068/, https://github.com/nodejs/node/pull/45098/)
Appeared test-rackspace-win2012r2_vs2019-x64-1, test-nearform-macos10.15-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47425/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47485/
Example
not ok 849 pummel/test-fs-largefile
  ---
  duration_ms: 0.945
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.850
    Files blocking: [ 'large.txt' ]
    
    node:internal/fs/utils:347
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, ftruncate
        at Object.ftruncateSync (node:fs:1130:3)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\pummel\test-fs-largefile.js:37:4)
        at Module._compile (node:internal/modules/cjs/loader:1175:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1229:10)
        at Module.load (node:internal/modules/cjs/loader:1038:32)
        at Module._load (node:internal/modules/cjs/loader:879:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:82:12)
        at node:internal/main/run_main_module:23:47 {
      errno: -4055,
      syscall: 'ftruncate',
      code: 'ENOSPC'...

Reason addons/request-interrupt/test
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/45098/, https://github.com/nodejs/node/pull/45127/, https://github.com/nodejs/node/pull/45175/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/47420/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47498/
Example
not ok 3506 addons/request-interrupt/test
  ---
  duration_ms: 300.177
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason node-api/test_fatal/test2
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/45132/, https://github.com/nodejs/node/pull/44412/, https://github.com/nodejs/node/pull/45175/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/47422/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47498/
Example
not ok 3607 node-api/test_fatal/test2
  ---
  duration_ms: 300.177
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-heapsnapshot-near-heap-limit-by-api-in-worker
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/45153/, https://github.com/nodejs/node/pull/45157/)
Appeared test-osuosl-rhel8-ppc64_le-1, test-equinix-ubuntu2004_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47459/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47470/
Example
not ok 1198 parallel/test-heapsnapshot-near-heap-limit-by-api-in-worker
  ---
  duration_ms: 2.586
  severity: fail
  exitcode: 1
  stack: |-
    
    Invoked NearHeapLimitCallback, processing=false, current_limit=52428800, initial_limit=52428800
    max_young_gen_size=50331648, young_gen_size=0, old_gen_size=51371528, total_size=51371528
    Estimated available memory=9223372036742447104, estimated overhead=50331648
    Start generating Heap.20221025.113252.2579039.1.001.heapsnapshot...
    Invoked NearHeapLimitCallback, processing=true, current_limit=52428800, initial_limit=52428800
    max_young_gen_size=50331648, young_gen_size=0, old_gen_size=51371528, total_size=51371528
    Estimated available memory=9223372036742447104, estimated overhead=50331648
    Not generating snapshots in nested callback. new_limit=102760448
    1/1 snapshots taken.
    Removing the near heap limit callbackWrote snapshot to /home/iojs/node-tmp/.tmp.1193/Heap.20221025.113252.2579039.1.001.heapsnapshot
    
    <--- Last few GCs ...

Reason parallel/test-runner-inspect
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/43525/, https://github.com/nodejs/node/pull/44412/)
Appeared test-ibm-rhel8-s390x-4, test-azure_msft-win10_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/47423/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47440/
Example
not ok 3355 parallel/test-runner-inspect
  ---
  duration_ms: 120.41
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] (node:4128394) Warning: Using the inspector with --test forces running at a concurrency of 1. Use the inspectPort option to run with concurrency
    [err] (Use `node --trace-warnings ...` to show where the warning was created)
    [err] 
    [out] TAP version 13
    [out] 
    [err] Debugger listening on ws://127.0.0.1:46757/1075ad56-be7b-4084-9c58-15c36a17f4a7
    [err] 
    [err] Debugger attached.
    [err] 
  ...


Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/45092/, https://github.com/nodejs/node/pull/45157/, https://github.com/nodejs/node/pull/45195/)
Appeared test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47416/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47500/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:26715' 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)

Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/44412/, https://github.com/nodejs/node/pull/45098/, https://github.com/nodejs/node/pull/45175/)
Appeared test-softlayer-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47440/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47496/
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 2 (https://github.com/nodejs/node/pull/45153/, https://github.com/nodejs/node/pull/45117/)
Appeared test-rackspace-win2012r2_vs2019-x64-6, test-rackspace-win2012r2_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47459/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47469/
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

Progress
  • pummel/test-fs-readfile-tostring-fail (8)
  • parallel/test-watch-mode-files_watcher (4)
  • pummel/test-fs-largefile (4)
  • addons/request-interrupt/test (3)
  • node-api/test_fatal/test2 (3)
  • parallel/test-heapsnapshot-near-heap-limit-by-api-in-worker (2)
  • parallel/test-runner-inspect (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
  • Build timed out (after 60 minutes). Marking the build as failed. (3)
  • error: remote GitHub already exists. (2)
Langage dominant
Shell
Étoiles
57
Forks
20
Métriques de merge des PR
Aucune PR mergée en 30 j

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nodejs/reliability

Toutes les issues de nodejs/reliability

Issues similaires

Plus d'issues Shell/Bash

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.