nodejs / nodejs/reliability

CI Reliability 2024-06-18

Offen
#899 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/59755 to node-test-pull-request/59849 that failed 2 or more 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
2024-06-18 00:08 2 12 22 2 62 12.50%
Jenkins Failure
Reason Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node-test-commit-linux"): error=2, No such file or directory
Type JENKINS_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/52135/, https://github.com/nodejs/node/pull/53063/, https://github.com/nodejs/node/pull/53465/, https://github.com/nodejs/node/pull/53486/, https://github.com/nodejs/node/pull/53468/)
Appeared test-digitalocean-fedora38-x64-2, test-ibm-rhel9-x64-1, test-digitalocean-fedora38-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/59844/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59849/
Example
java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node-test-commit-linux"): error=2, No such file or directory
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
	at hudson.Proc$LocalProc.<init>(Proc.java:252)
	at hudson.Proc$LocalProc.<init>(Proc.java:221)
	at hudson.Launcher$LocalLauncher.launch(Launcher.java:994)

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/50983/, https://github.com/nodejs/node/pull/53063/)
Appeared test-rackspace-win2022_vs2022-x64-2, test-ibm-rhel8-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/59759/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59843/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 104.130.74.162/104.130.74.162:49701' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy103.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1212)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1204)

Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53063/, https://github.com/nodejs/node/pull/53463/)
Appeared test-ibm-ubi81_container-x64-1, test-digitalocean-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/59769/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59802/
Example
Build timed out (after 60 minutes). Marking the build as failed.

Git Failure
Build Failure
Reason fatal: No rebase in progress?
Type BUILD_FAILURE
Failed PR 9 (https://github.com/nodejs/node/pull/53431/, https://github.com/nodejs/node/pull/53442/, https://github.com/nodejs/node/pull/53063/, https://github.com/nodejs/node/pull/53157/, https://github.com/nodejs/node/pull/53438/, https://github.com/nodejs/node/pull/53455/, https://github.com/nodejs/node/pull/53459/, https://github.com/nodejs/node/pull/53467/, https://github.com/nodejs/node/pull/53486/)
Appeared test-ibm-ubuntu2204_sharedlibs_container-x64-3, test-ibm-ubuntu2204_sharedlibs_container-x64-4, test-ibm-ubuntu2204_sharedlibs_container-x64-1, test-ibm-ubuntu2204_sharedlibs_container-x64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/59758/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59842/
Example
fatal: No rebase in progress?

Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/53452/, https://github.com/nodejs/node/pull/53239/, https://github.com/nodejs/node/pull/53456/, https://github.com/nodejs/node/pull/53477/, https://github.com/nodejs/node/pull/52135/)
Appeared test-mnx-smartos21-x64-2, test-mnx-smartos23-x64-1, test-equinix-debian11_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian11_container-armv7l-2, test-osuosl-ubuntu2004_container-armv7l-1, test-osuosl-debian11_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/59785/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59844/
Example
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason Error: invalid syntax
Type BUILD_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/53462/, https://github.com/nodejs/node/pull/53465/, https://github.com/nodejs/node/pull/53411/, https://github.com/nodejs/node/pull/53488/, https://github.com/nodejs/node/pull/53486/)
Appeared test-orka-macos10.15-x64-2, test-rackspace-debian10-x64-1, test-orka-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/59835/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59841/
Example
Error: invalid syntax
make: *** [build-ci] Error 1
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for : : True
Logical operation result is TRUE

Reason fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)
Type BUILD_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/53411/, https://github.com/nodejs/node/pull/53488/, https://github.com/nodejs/node/pull/53063/, https://github.com/nodejs/node/pull/53468/)
Appeared test-orka-macos11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/59839/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59849/
Example
fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)

JSTest Failure
Reason sequential/test-http-server-request-timeouts-mixed
Type JS_TEST_FAILURE
Failed PR 6 (https://github.com/nodejs/node/pull/53442/, https://github.com/nodejs/node/pull/53411/, https://github.com/nodejs/node/pull/53463/, https://github.com/nodejs/node/pull/53467/, https://github.com/nodejs/node/pull/53465/, https://github.com/nodejs/node/pull/53413/)
Appeared test-orka-macos11-x64-1, test-orka-macos11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/59761/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59834/
Example
not ok 4117 sequential/test-http-server-request-timeouts-mixed
  ---
  duration_ms: 3151.80000
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:408
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
    
      assert(request2.completed)
    
        at Timeout._onTimeout (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/sequential/test-http-server-request-timeouts-mixed.js:108:5)
        at listOnTimeout (node:internal/timers:581:17)
        at process.processTimers (node:internal/timers:519:7) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v23.0.0-pre
  ...


Reason benchmark/test-benchmark-crypto
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/53431/, https://github.com/nodejs/node/pull/51344/, https://github.com/nodejs/node/pull/53438/, https://github.com/nodejs/node/pull/53488/)
Appeared test-ibm-ubuntu2204_sharedlibs_container-x64-3, test-digitalocean-ubuntu2204_sharedlibs_container-x64-10, test-equinix-ubuntu2004_sharedlibs_container-arm64-5, test-ibm-ubuntu2204_sharedlibs_container-x64-2, test-digitalocean-ubuntu2204_sharedlibs_container-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/59760/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59840/
Example
not ok 4021 benchmark/test-benchmark-crypto
  ---
  duration_ms: 4392.63000
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:126
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    1 !== 0
    
        at main (/home/iojs/build/workspace/node-test-commit-linux-containered/benchmark/crypto/timingSafeEqual.js:21:10)
        at /home/iojs/build/workspace/node-test-commit-linux-containered/benchmark/common.js:54:9
        at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: 1,
      expected: 0,
      operator: 'strictEqual'
    }
    
    Node.js v23.0.0-pre
    node:assert:126
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    1 !== 0
    
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/...

Reason parallel/test-cli-node-options
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/53486/, https://github.com/nodejs/node/pull/53063/, https://github.com/nodejs/node/pull/52135/, https://github.com/nodejs/node/pull/53465/)
Appeared test-rackspace-win2019_vs2019-x64-1, test-rackspace-win2019_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/59842/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59847/
Example
not ok 121 parallel/test-cli-node-options
  ---
  duration_ms: 1341.04800
  severity: crashed
  exitcode: 2147483651
  stack: |-
    
    <--- Last few GCs --->
    
    
    <--- JS stacktrace --->
    
    FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
    ----- Native stack trace -----
    
    
    #
    # Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
    #
    
  ...


Reason parallel/test-pipe-file-to-http
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/51344/, https://github.com/nodejs/node/pull/53464/, https://github.com/nodejs/node/pull/53472/, https://github.com/nodejs/node/pull/53475/)
Appeared test-osuosl-debian11_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian11_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/59773/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59833/
Example
not ok 2835 parallel/test-pipe-file-to-http
  ---
  duration_ms: 360022.08500
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-require-symlink
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/53486/, https://github.com/nodejs/node/pull/53063/, https://github.com/nodejs/node/pull/52135/, https://github.com/nodejs/node/pull/53465/)
Appeared test-azure_msft-win2016_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/59842/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59847/
Example
not ok 660 parallel/test-require-symlink
  ---
  duration_ms: 429.00500
  severity: crashed
  exitcode: 3221225477
  stack: |-
  ...


Reason parallel/test-performance-function
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/53456/, https://github.com/nodejs/node/pull/53431/, https://github.com/nodejs/node/pull/53475/)
Appeared test-ibm-ubuntu2204-x64-2, test-ibm-rhel8-x64-2, test-ibm-rhel8-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/59797/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59833/
Example
not ok 2445 parallel/test-performance-function
  ---
  duration_ms: 337.65100
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/histogram:291
        validateInteger(val, 'val', 1);
        ^
    
    RangeError [ERR_OUT_OF_RANGE]: The value of "val" is out of range. It must be >= 1 && <= 9007199254740991. Received 0
        at RecordableHistogram.record (node:internal/histogram:291:5)
        at processComplete (node:internal/perf/timerify:40:15)
        at timerified m (node:internal/perf/timerify:87:5)
        at /home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-performance-function.js:103:5
        at runNextTicks (node:internal/process/task_queues:60:5)
        at listOnTimeout (node:internal/timers:545:9)
        at process.processTimers (node:internal/timers:519:7) {
      code: 'ERR_OUT_OF_RANGE'
    }
    
    Node.js v23.0.0-pre
  ...


Reason parallel/test-worker-memory
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/53455/, https://github.com/nodejs/node/pull/53057/, https://github.com/nodejs/node/pull/53486/)
Appeared test-azure_msft-win10_vs2019-x64-2, test-rackspace-win2022_vs2022-x64-3, test-azure_msft-win10_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/59790/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59846/
Example
not ok 890 parallel/test-worker-memory
  ---
  duration_ms: 1816.00500
  severity: crashed
  exitcode: 3221225477
  stack: |-
    run() called with n=15 (numWorkers=4)
    run() called with n=15 (numWorkers=4)
    run() called with n=15 (numWorkers=4)
    run() called with n=15 (numWorkers=4)
    run() called with n=14 (numWorkers=4)
    run() called with n=14 (numWorkers=4)
    run() called with n=14 (numWorkers=4)
    run() called with n=14 (numWorkers=4)
    run() called with n=13 (numWorkers=4)
    run() called with n=13 (numWorkers=4)
    run() called with n=13 (numWorkers=4)
    run() called with n=13 (numWorkers=4)
    run() called with n=12 (numWorkers=4)
    run() called with n=12 (numWorkers=4)
    run() called with n=12 (numWorkers=4)
    run() called with n=12 (numWorkers=4)
    run() called with n=11 (numWorkers=4)
    run() called with n=11 (numWorkers=4)
    run() called with n=11 (numWorkers=4)
    run() called with n=11 (numWorkers=4)
    run() called with n=10 (numWorkers=4)
    run() called...

Reason benchmark/test-benchmark-child-process
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53439/, https://github.com/nodejs/node/pull/53442/)
Appeared test-osuosl-debian11_container-armv7l-1, test-osuosl-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/59755/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59761/
Example
not ok 171 benchmark/test-benchmark-child-process
  ---
  duration_ms: 2160099.51100
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-file-write-stream4
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53441/, https://github.com/nodejs/node/pull/53468/)
Appeared test-equinix-ubuntu2004_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/59757/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59849/
Example
not ok 3917 parallel/test-file-write-stream4
  ---
  duration_ms: 360071.57700
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-net-write-fully-async-buffer
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53455/, https://github.com/nodejs/node/pull/53456/)
Appeared test-equinix_mnx-smartos20-x64-3, test-equinix-ubuntu2004_sharedlibs_container-arm64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/59790/
Last CI https://ci.nodejs.org/job/node-test-pull-request/59797/
Example
not ok 3803 parallel/test-net-write-fully-async-buffer
  ---
  duration_ms: 300181.54700
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Progress
  • Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node-test-commit-linux"): error=2, No such file or directory (5)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • fatal: No rebase in progress? (9)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (5)
  • Error: invalid syntax (5)
  • fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device) (4)
  • sequential/test-http-server-request-timeouts-mixed (6)
  • benchmark/test-benchmark-crypto (4)
  • parallel/test-cli-node-options (4)
  • parallel/test-pipe-file-to-http (4)
  • parallel/test-require-symlink (4)
  • parallel/test-performance-function (3)
  • parallel/test-worker-memory (3)
  • benchmark/test-benchmark-child-process (2)
  • parallel/test-file-write-stream4 (2)
  • parallel/test-net-write-fully-async-buffer (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 damit, die verknüpften Jenkins-CI-Konsolenprotokolle zu überprüfen und die gemeldeten Gründe für JENKINS_FAILURE und BUILD_FAILURE zu gruppieren. Das Issue nennt keine Dateien, Tests, spezifische Änderung oder Abschlussprüfung, daher muss vor der Implementierung festgelegt werden, was als abgeschlossen gilt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
shell
Bereich
ci-cd, devops
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

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