nodejs / nodejs/reliability

CI Reliability 2023-09-02

Aperta
#653 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/53586 to node-test-pull-request/53684 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
2023-09-02 00:11 1 0 27 0 72 0.00%
Jenkins Failure
Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 6 (https://github.com/nodejs/node/pull/49327/, https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49155/, https://github.com/nodejs/node/pull/49275/, https://github.com/nodejs/node/pull/49161/, https://github.com/nodejs/node/pull/49312/)
Appeared test-rackspace-win2019_vs2019-x64-2, test-digitalocean-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53608/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53663/
Example
Build timed out (after 60 minutes). Marking the build as failed.

CCTest Failure
Reason Value of: (!expectation.read_expected)
Type CC_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/48919/, https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49413/)
Appeared test-digitalocean-alpine315_container-x64-2, test-digitalocean-alpine318_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53594/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53660/
Example
Value of: (!expectation.read_expected)
  Actual: true
Expected: false

[  FAILED  ] InspectorSocketTest.HostIPv6NonRoutable (5000 ms)

Git Failure
Reason ERROR: Error fetching remote repo 'origin'
Type GIT_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/49220/, https://github.com/nodejs/node/pull/49274/, https://github.com/nodejs/node/pull/49185/)
Appeared test-ibm-ubuntu1804-x64-1, test-softlayer-debian10-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-digitalocean-ubuntu1804_sharedlibs_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-6, test-digitalocean-ubuntu1804_sharedlibs_container-x64-7, undefined, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/53678/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53684/
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:999)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1241)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1305)
	at hudson.scm.SCM.checkout(SCM.java:540)

Build Failure
Reason Failed to trigger fanned build
Type BUILD_FAILURE
Failed PR 11 (https://github.com/nodejs/node/pull/49320/, https://github.com/nodejs/node/pull/49274/, https://github.com/nodejs/node/pull/49348/, https://github.com/nodejs/node/pull/49346/, https://github.com/nodejs/node/pull/48919/, https://github.com/nodejs/node/pull/49239/, https://github.com/nodejs/node/pull/49161/, https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49238/, https://github.com/nodejs/node/pull/49340/)
Appeared undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/53587/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53602/
Example
Failed to trigger fanned build

Reason sh: line 0: printf: write error: No space left on device
Type BUILD_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/49327/, https://github.com/nodejs/node/pull/49404/, https://github.com/nodejs/node/pull/49397/, https://github.com/nodejs/node/pull/49391/)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53608/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53654/
Example
sh: line 0: printf: write error: No space left on device

Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/49220/)
Appeared test-equinix-rhel8_container-arm64-2, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-4, test-equinix-ubuntu2004_container-armv7l-2, test-equinix_mnx-smartos20-x64-3, test-equinix-ubuntu2004_sharedlibs_container-arm64-3, test-osuosl-aix72-ppc64_be-2, test-osuosl-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53614/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53630/
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: Step �Publish JUnit test result report� failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49275/)
Appeared test-azure_msft-win2022_vs2019-x64-3, test-azure_msft-win11_vs2022-arm64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/53623/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53638/
Example
ERROR: Step �Publish JUnit test result report� failed: no workspace for node-test-binary-windows-js-suites/RUN_SUBSET=3,nodes=win2022-COMPILED_BY-vs2019 #22796
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

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 2 (https://github.com/nodejs/node/pull/49155/, https://github.com/nodejs/node/pull/49335/)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53636/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53662/
Example
fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)

Reason fatal: No rebase in progress?
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/49220/, https://github.com/nodejs/node/pull/49400/)
Appeared test-nearform-macos10.15-x64-1, test-digitalocean-alpine315_container-x64-2, test-digitalocean-alpine318_container-x64-2, test-rackspace-debian10-x64-1, test-rackspace-fedora32-x64-1, test-digitalocean-fedora38-x64-1, test-ibm-rhel8-x64-1, test-orka-macos11-x64-2, test-osuosl-rhel8-ppc64_le-3, test-digitalocean-ubi81_container-x64-1, test-macstadium-macos11.0-arm64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/53630/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53639/
Example
fatal: No rebase in progress?

JSTest Failure
Reason sequential/test-http-regr-gh-2928
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/49238/, https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49161/, https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/49423/)
Appeared test-rackspace-win2012r2_vs2015-x64-2, test-digitalocean-freebsd12-x64-2, test-rackspace-win2012r2_vs2019-x64-1, test-digitalocean-freebsd12-x64-1, test-azure_msft-win2016_vs2017-x64-6
First CI https://ci.nodejs.org/job/node-test-pull-request/53603/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53675/
Example
not ok 933 sequential/test-http-regr-gh-2928
  ---
  duration_ms: 1240.00400
  severity: fail
  exitcode: 3221226505
  stack: |-
    .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+....

Reason node-api/test_threadsafe_function/test
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/49341/, https://github.com/nodejs/node/pull/49401/, https://github.com/nodejs/node/pull/49400/)
Appeared test-equinix-ubuntu2004_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53605/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53639/
Example
not ok 3793 node-api/test_threadsafe_function/test
  ---
  duration_ms: 360048.10300
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-blob-file-backed
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/49404/, https://github.com/nodejs/node/pull/48655/, https://github.com/nodejs/node/pull/49391/, https://github.com/nodejs/node/pull/49274/)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4, test-ibm-rhel8-s390x-1, test-ibm-rhel8-s390x-4, test-digitalocean-ubuntu1804-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53642/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53659/
Example
not ok 200 parallel/test-blob-file-backed
  ---
  duration_ms: 458.42300
  severity: fail
  exitcode: 1
  stack: |-
    
    node:internal/per_context/domexception:53
        ErrorCaptureStackTrace(this);
        ^
    DOMException [NotReadableError]: The blob could not be read
        at new DOMException (node:internal/per_context/domexception:53:5)
        at __node_internal_ (node:internal/util:665:10)
        at BlobReader.<anonymous> (node:internal/blob:289:25)
    
    Node.js v21.0.0-pre
  ...


Reason parallel/test-inspector-stop-profile-after-done
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/49346/, https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49413/, https://github.com/nodejs/node/pull/49391/)
Appeared test-ibm-rhel8-s390x-4, test-ibm-rhel8-s390x-1, test-ibm-rhel8-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/53590/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53682/
Example
not ok 3636 parallel/test-inspector-stop-profile-after-done
  ---
  duration_ms: 120099.14000
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:45067/2a7478eb-0811-41ec-bc8a-b835fff5b977
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] 
  ...


Reason sequential/test-worker-prof
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/49346/, https://github.com/nodejs/node/pull/49161/, https://github.com/nodejs/node/pull/49404/, https://github.com/nodejs/node/pull/49288/)
Appeared test-rackspace-win2022_vs2022-x64-1, test-azure_msft-win2022_vs2019-x64-3, test-rackspace-win2022_vs2022-x64-3, test-macstadium-macos11.0-arm64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/53590/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53680/
Example
not ok 948 sequential/test-worker-prof
  ---
  duration_ms: 2295.02800
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child exited with non-zero status:                      {
      status: 3221226505,
      signal: null,
      output: [ null, '', '' ],
      pid: 7716,
      stdout: '',
      stderr: ''
    }
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:60:10)
        at Module._compile (node:internal/modules/cjs/loader:1241:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
        at Module.load (node:internal/modules/cjs/loader:1091:32)
        at Module._load (node:internal/modules/cjs/loader:938:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47 {
      generatedMessage: false,
      code: 'ERR_ASSERTIO...

Reason parallel/test-runner-watch-mode
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/49401/, https://github.com/nodejs/node/pull/49155/, https://github.com/nodejs/node/pull/49340/)
Appeared test-osuosl-ubuntu2004_container-armv7l-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53617/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53665/
Example
not ok 2825 parallel/test-runner-watch-mode
  ---
  duration_ms: 360047.37200
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    TAP version 13
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    Updating /home/iojs/tmp/.tmp.2346/dependent.js
    # Subtest: test runner watch mode
        # Subtest: should run tests repeatedly
        ok 1 - should run tests repeatedly
          ---
          duration_ms: 1287.004742
          ...


Reason sequential/test-single-executable-application-snapshot-and-code-cache
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/49274/, https://github.com/nodejs/node/pull/49400/, https://github.com/nodejs/node/pull/49401/)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-equinix-ubuntu2004_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/53588/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53617/
Example
not ok 3975 sequential/test-single-executable-application-snapshot-and-code-cache
  ---
  duration_ms: 10665.40800
  severity: fail
  exitcode: 1
  stack: |-
    warning: Can't find string offset for section name '.note'
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    + actual - expected
    
    + ''
    - 'Hello from snapshot'
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/sequential/test-single-executable-application-snapshot-and-code-cache.js:62:10)
        at Module._compile (node:internal/modules/cjs/loader:1241:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
        at Module.load (node:internal/modules/cjs/loader:1091:32)
        at Module._load (node:internal/modules/cjs/loader:938:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_mod...

Reason parallel/test-crypto-dh
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/49275/, https://github.com/nodejs/node/pull/49423/)
Appeared test-rackspace-win2012r2_vs2019-x64-2, test-rackspace-win2012r2_vs2015-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/53648/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53675/
Example
not ok 907 parallel/test-crypto-dh
  ---
  duration_ms: 120148.99500
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason parallel/test-http-remove-connection-header-persists-connection
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/49275/, https://github.com/nodejs/node/pull/49274/)
Appeared test-ibm-rhel8-s390x-3, test-ibm-rhel8-s390x-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53634/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53655/
Example
not ok 1271 parallel/test-http-remove-connection-header-persists-connection
  ---
  duration_ms: 477.53200
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    false !== true
    
        at /home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-http-remove-connection-header-persists-connection.js:67:16
        at Timeout._onTimeout (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-http-remove-connection-header-persists-connection.js:54:7)
        at listOnTimeout (node:internal/timers:573:17)
        at process.processTimers (node:internal/timers:514:7) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: 'strictEqual'
    }
    
    Node.js v21.0.0-pre
  ...


Reason pummel/test-heapdump-shadow-realm
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/49397/)
Appeared test-rackspace-debian10-x64-1, test-softlayer-debian10-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53605/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53646/
Example
not ok 3616 pummel/test-heapdump-shadow-realm
  ---
  duration_ms: 50765.08400
  severity: crashed
  exitcode: -6
  stack: |-
    
    <--- Last few GCs --->
    
    [14959:0x561503e4bbb0]    48729 ms: Mark-Compact (reduce) 996.0 (1012.6) -> 995.2 (1012.9) MB, 1033.82 / 0.01 ms  (+ 159.2 ms in 42 steps since start of marking, biggest step 18.3 ms, walltime since start of marking 1386 ms) (average mu = 0.315, current m[14959:0x561503e4bbb0]    50369 ms: Mark-Compact (reduce) 996.1 (1012.9) -> 995.8 (1013.4) MB, 1322.75 / 0.01 ms  (+ 62.9 ms in 10 steps since start of marking, biggest step 13.3 ms, walltime since start of marking 1397 ms) (average mu = 0.243, current mu
    
    <--- JS stacktrace --->
    
    FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
     1: 0x5614fe8904d0 node::Abort() [out/Release/node]
     2: 0x5614fe76b515  [out/Release/node]
     3: 0x5614feaccfb0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [out/Release...

Reason sequential/test-cli-syntax-require
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49185/)
Appeared test-ibm-rhel8-s390x-4, test-osuosl-aix72-ppc64_be-3, test-ibm-aix72-ppc64_be-2
First CI https://ci.nodejs.org/job/node-test-pull-request/53658/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53684/
Example
not ok 3879 sequential/test-cli-syntax-require
  ---
  duration_ms: 91.10400
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:1026
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The input did not match the regular expression /^SyntaxError: \b/m. Input:
    
    ''
    
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/sequential/test-cli-syntax-require.js:34:14)
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/common/index.js:466:15)
        at ChildProcess.emit (node:events:514:28)
        at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '',
      expected: /^SyntaxError: \b/m,
      operator: 'match'
    }
    
    Node.js v20.6.1-pre
  ...


Reason sequential/test-perf-hooks
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/49346/, https://github.com/nodejs/node/pull/49161/)
Appeared test-azure_msft-win11_vs2022-arm64-6, undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/53590/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53667/
Example
not ok 932 sequential/test-perf-hooks
  ---
  duration_ms: 229.23600
  severity: fail
  exitcode: 1
  stack: |-
    check initial nodeTiming
    {
      "name": "node",
      "entryType": "node",
      "startTime": 0,
      "duration": 147.57630002498627,
      "nodeStart": 0.7022000551223755,
      "v8Start": 5.008900046348572,
      "environment": 19.22030007839203,
      "loopStart": -1,
      "loopExit": -1,
      "bootstrapComplete": 73.78420007228851,
      "idleTime": 0
    }
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: now (160.24030005931854) - timing.duration (147.57630002498627) = 12.664000034332275 >= 10
        at checkNodeTiming (d:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-perf-hooks.js:104:3)
        at Object.<anonymous> (d:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-perf-hooks.js:119:1)
        at Module._compile (node:internal/modules/cjs/loader:1241:14)
        at Module._extensions..js (n...

Reason sequential/test-single-executable-application-snapshot
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/49423/, https://github.com/nodejs/node/pull/49413/)
Appeared test-azure_msft-win2016_vs2017-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/53674/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53683/
Example
not ok 936 sequential/test-single-executable-application-snapshot
  ---
  duration_ms: 21291.67600
  severity: fail
  exitcode: 1
  stack: |-
    Aborted()
    node:child_process:929
        throw err;
        ^
    
    Error: Command failed: C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe C:\workspace\node-test-binary-windows-js-suites\node\test\fixtures\postject-copy\node_modules\postject\dist\cli.js C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.935\sea.exe NODE_SEA_BLOB C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.935\sea-prep.blob --sentinel-fuse NODE_SEA_FUSE_fce680ab2cc467b6e072b8b5df1996b2
    Aborted()
    
        at checkExecSyncError (node:child_process:890:11)
        at execFileSync (node:child_process:926:15)
        at injectAndCodeSign (C:\workspace\node-test-binary-windows-js-suites\node\test\common\sea.js:48:3)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-single-executable-ap...

Progress
  • Build timed out (after 60 minutes). Marking the build as failed. (6)
  • Value of: (!expectation.read_expected) (4)
  • ERROR: Error fetching remote repo 'origin' (3)
  • Failed to trigger fanned build (11)
  • sh: line 0: printf: write error: No space left on device (4)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • ERROR: Step �Publish JUnit test result report� failed: no workspace for ... (2)
  • fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device) (2)
  • fatal: No rebase in progress? (2)
  • sequential/test-http-regr-gh-2928 (5)
  • node-api/test_threadsafe_function/test (4)
  • parallel/test-blob-file-backed (4)
  • parallel/test-inspector-stop-profile-after-done (4)
  • sequential/test-worker-prof (4)
  • parallel/test-runner-watch-mode (3)
  • sequential/test-single-executable-application-snapshot-and-code-cache (3)
  • parallel/test-crypto-dh (2)
  • parallel/test-http-remove-connection-header-persists-connection (2)
  • pummel/test-heapdump-shadow-realm (2)
  • sequential/test-cli-syntax-require (2)
  • sequential/test-perf-hooks (2)
  • sequential/test-single-executable-application-snapshot (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 con le esecuzioni CI di node-test-pull-request collegate e i log della console di esempio, raggruppando per causa i fallimenti segnalati di Jenkins, CCTest, Git, build e JSTest. L’issue non fornisce file sorgente, test da modificare né una singola condizione di completamento; il lavoro sarebbe concluso quando i problemi di affidabilità sottostanti nei job CI interessati saranno identificati e risolti.

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

Valutazione

Stack tecnologico
git, shell
Ambito
ci-cd, devops, 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
15/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.