nodejs / nodejs/reliability

CI Reliability 2022-10-18

Offen
#403 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

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/47213 to node-test-pull-request/47308 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-18 00:21 1 17 21 6 55 18.28%
Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44980/, https://github.com/nodejs/node/pull/44950/)
Appeared test-digitalocean-freebsd12-x64-2, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47240/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47285/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:61698' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy92.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1215)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1207)

Git Failure
Build Failure
Reason error: remote GitHub already exists.
Type BUILD_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/44978/, https://github.com/nodejs/node/pull/44869/, https://github.com/nodejs/node/pull/44968/, https://github.com/nodejs/node/pull/44250/)
Appeared test-rackspace-win2012r2_vs2019-x64-1, test-rackspace-win2012r2_vs2017-x64-1, test-rackspace-win2012r2_vs2019-x64-5, test-rackspace-win2012r2_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/47215/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47257/
Example
error: remote GitHub already exists.

> git fetch --prune --no-tags GitHub 
From https://github.com/nodejs/build
   8dad541..45137d5  main       -> GitHub/main

Reason Error: [WinError 5] Access is denied: 'C:\Users\Administrator\clcache\stats.txt.new' -> 'C:\Users\Administrator\clcache\stats.txt'
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44968/, https://github.com/nodejs/node/pull/44626/)
Appeared test-rackspace-win2012r2_vs2019-x64-1, test-rackspace-win2012r2_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/47251/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47293/
Example
Error: [WinError 5] Access is denied: 'C:\\Users\\Administrator\\clcache\\stats.txt.new' -> 'C:\\Users\\Administrator\\clcache\\stats.txt'
  [5640] Failed to execute script clcache_main
  units_converter.cpp
  locid.cpp
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(523,5): error MSB6006: "clcache_main.exe" exited with code -1. [C:\workspace\node-compile-windows-debug\node\tools\icu\icui18n.vcxproj]
  lstmbe.cpp

JSTest Failure
Reason sequential/test-watch-mode-inspect
Type JS_TEST_FAILURE
Failed PR 6 (https://github.com/nodejs/node/pull/44917/, https://github.com/nodejs/node/pull/44869/, https://github.com/nodejs/node/pull/44983/, https://github.com/nodejs/node/pull/44968/, https://github.com/nodejs/node/pull/44250/, https://github.com/nodejs/node/pull/45041/)
Appeared test-nearform-macos10.15-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-2, test-nearform-macos10.15-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47219/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47306/
Example
not ok 3800 sequential/test-watch-mode-inspect
  ---
  duration_ms: 120.103
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    [test] Connecting to a child Node process
    [test] Testing /json/list
    TAP version 13
    [err] (node:10346) ExperimentalWarning: Watch mode is an experimental feature. This feature could change at any time
    [err] (Use `node --trace-warnings ...` to show where the warning was created)
    [err] 
    [err] Debugger listening on ws://127.0.0.1:54291/0f69e497-659d-4d62-a7e5-4b93a72d0d56
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] 
    [out] safe to debug now
    [out] 
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger ending on ws://127.0.0.1:54291/0f69e497-659d-4d62-a7e5-4b93a72d0d56
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
  ...


Reason pummel/test-fs-readfile-tostring-fail
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/44935/, https://github.com/nodejs/node/pull/44917/, https://github.com/nodejs/node/pull/44983/, https://github.com/nodejs/node/pull/44250/, https://github.com/nodejs/node/pull/44970/)
Appeared test-orka-macos11-x64-2, test-nearform-macos10.15-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47213/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47268/
Example
not ok 3400 pummel/test-fs-readfile-tostring-fail
  ---
  duration_ms: 0.168
  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-corepack-yarn-install
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/44978/, https://github.com/nodejs/node/pull/44731/, https://github.com/nodejs/node/pull/44968/, https://github.com/nodejs/node/pull/45032/)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/47215/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47291/
Example
not ok 592 parallel/test-corepack-yarn-install
  ---
  duration_ms: 2.744
  severity: fail
  exitcode: 1
  stack: |-
    (node:29517) [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 Socket.<anonymous> (internal/chi...

Reason pummel/test-fs-largefile
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/44917/, https://github.com/nodejs/node/pull/44731/, https://github.com/nodejs/node/pull/44984/)
Appeared test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-1, test-nearform-macos10.15-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47214/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47236/
Example
not ok 843 pummel/test-fs-largefile
  ---
  duration_ms: 0.943
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.843
    Files blocking: [ 'large.txt' ]
    
    node:internal/fs/utils:348
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, ftruncate
        at Object.ftruncateSync (node:fs:1137: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: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:81:12)
        at node:internal/main/run_main_module:23:47 {
      errno: -4055,
      syscall: 'ftruncate',
      code: 'ENOSPC'...

Reason sequential/test-perf-hooks
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/44968/, https://github.com/nodejs/node/pull/44626/, https://github.com/nodejs/node/pull/45042/)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-6, test-softlayer-ubuntu1804_sharedlibs_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47242/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47301/
Example
not ok 3796 sequential/test-perf-hooks
  ---
  duration_ms: 1.913
  severity: fail
  exitcode: 1
  stack: |-
    {
      name: 'node',
      entryType: 'node',
      startTime: 0,
      duration: { around: 34.9045524597168 },
      nodeStart: { around: 0 },
      v8Start: { around: 0 },
      bootstrapComplete: { around: 34.8656005859375, delay: 2500 },
      environment: { around: 0 },
      loopStart: -1,
      loopExit: -1
    }
    {
      name: 'node',
      entryType: 'node',
      startTime: 0,
      duration: { around: 1039.352783203125 },
      nodeStart: { around: 0 },
      v8Start: { around: 0 },
      bootstrapComplete: { around: 34.8656005859375, delay: 2500 },
      environment: { around: 0 },
      loopStart: { around: 34.8656005859375, delay: 2500 },
      loopExit: -1
    }
    {
      name: 'node',
      entryType: 'node',
      startTime: 0,
      duration: { around: 1758.757698059082 },
      nodeStart: { around: 0 },
      v8Start: { around: 0 },
      bootstrapComplete: { around: 34.865...

Reason abort/test-abort-backtrace
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44731/, https://github.com/nodejs/node/pull/45032/)
Appeared test-joyent-smartos20-x64-3, test-joyent-smartos20-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/47227/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47294/
Example
not ok 3638 abort/test-abort-backtrace
  ---
  duration_ms: 300.168
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason abort/test-addon-uv-handle-leak
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44983/, https://github.com/nodejs/node/pull/44626/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/47229/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47300/
Example
not ok 3640 abort/test-addon-uv-handle-leak
  ---
  duration_ms: 300.97
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-child-process-exec-timeout-kill
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44968/, https://github.com/nodejs/node/pull/44626/)
Appeared test-digitalocean-freebsd12-x64-1, test-digitalocean-freebsd12-x64-2, test-ibm-rhel8-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/47223/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47300/
Example
not ok 283 parallel/test-child-process-exec-timeout-kill
  ---
  duration_ms: 0.395
  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:420:5)
        at ChildProcess.emit (node:events:513:28)
        at maybeClose (node:internal/child_process:1098:16)
        at Socket.<anonymous> (node:internal/child_process:456:11)
        at Socket.emit (node:events:513:28)
        at Pipe.<anonymous> (node:net:298:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: 1,
      expected: null,
      op...

Reason sequential/test-worker-prof
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44731/, https://github.com/nodejs/node/pull/44986/)
Appeared test-equinix-ubuntu1804_sharedlibs_container-arm64-2, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47227/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47254/
Example
not ok 3831 sequential/test-worker-prof
  ---
  duration_ms: 2.618
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:124
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child exited with an error:                      {
      status: null,
      signal: 'SIGTRAP',
      output: [
        null,
        '',
        '\n' +
          '\n' +
          '#\n' +
          '# Fatal error in ../deps/v8/src/libsampler/sampler.cc, line 584\n' +
          '# Debug check failed: IsActive().\n' +
          '#\n' +
          '#\n' +
          '#\n' +
          '#FailureMessage Object: 0xffff841b6588\n' +
          ' 1: 0xaaaacf148318 node::DumpBacktrace(_IO_FILE*) [/home/iojs/build/workspace/node-test-commit-arm-debug/out/Debug/node]\n' +
          ' 2: 0xaaaacf32ae30  [/home/iojs/build/workspace/node-test-commit-arm-debug/out/Debug/node]\n' +
          ' 3: 0xaaaacf32ae64  [/home/iojs/build/workspace/node-test-commit-arm-debug/out/Debug/node]\n' +
          ' 4: 0xaaaad0dffc30 ...

Reason wasi/test-wasi
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44862/, https://github.com/nodejs/node/pull/45032/)
Appeared test-osuosl-aix72-ppc64_be-3
First CI https://ci.nodejs.org/job/node-test-pull-request/47269/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47291/
Example
not ok 3393 wasi/test-wasi
  ---
  duration_ms: 0.978
  severity: fail
  exitcode: 1
  stack: |-
    executing cant_dotdot
    (node:6226428) ExperimentalWarning: WASI is an experimental feature. This feature could change at any time
    (Use `node --trace-warnings ...` to show where the warning was created)
    fd_prestat_get(3, 69720)
    fd_prestat_dir_name(3, 131088, 9)
    fd_prestat_get(4, 69720)
    fd_prestat_dir_name(4, 131152, 5)
    fd_prestat_get(5, 69720)
    environ_sizes_get(69724, 69720)
    environ_get(135168, 131168)
    fd_fdstat_get(3, 69672)
    path_open(3, 1, 1033, 14, 0, 264240830, 268435455, 0, 69668)
    
    executing clock_getres
    (node:6226430) ExperimentalWarning: WASI is an experimental feature. This feature could change at any time
    (Use `node --trace-warnings ...` to show where the warning was created)
    fd_prestat_get(3, 69688)
    fd_prestat_dir_name(3, 131088, 9)
    fd_prestat_get(4, 69688)
    fd_prestat_dir_name(4, 131152, 5)
    fd_prestat_get(5, 69688)
    envi...

Progress
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • error: remote GitHub already exists. (4)
  • Error: [WinError 5] Access is denied: 'C:\\Users\\Administrator\\clcache\\stats.txt.new' -> 'C:\\Users\\Administrator\\clcache\\stats.txt' (2)
  • sequential/test-watch-mode-inspect (6)
  • pummel/test-fs-readfile-tostring-fail (5)
  • parallel/test-corepack-yarn-install (4)
  • pummel/test-fs-largefile (3)
  • sequential/test-perf-hooks (3)
  • abort/test-abort-backtrace (2)
  • abort/test-addon-uv-handle-leak (2)
  • parallel/test-child-process-exec-timeout-kill (2)
  • sequential/test-worker-prof (2)
  • wasi/test-wasi (2)

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginne mit den verknüpften Jenkins-CI-Läufen und den aufgeführten Testpfaden, einschließlich test-watch-mode-inspect und test-fs-readfile-tostring-fail, um Infrastrukturfehler von Testfehlern zu trennen. Das Issue nennt keine Quelldatei, angeforderte Änderung oder Abschlusskriterium, daher müsste ein Beitragender zunächst die beabsichtigte Korrektur ermitteln, bevor er sie implementiert.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
git, node.js, shell
Bereich
ci-cd, devops, 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

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.