Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CI Reliability 2023-09-04 #655

Open
22 tasks
github-actions bot opened this issue Sep 4, 2023 · 0 comments
Open
22 tasks

CI Reliability 2023-09-04 #655

github-actions bot opened this issue Sep 4, 2023 · 0 comments

Comments

@github-actions
Copy link

github-actions bot commented Sep 4, 2023

Failures in node-test-pull-request/53610 to node-test-pull-request/53709 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-04 00:12 0 0 35 0 65 0.00%

Jenkins Failure

Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 6 (nodejs/node#49150, nodejs/node#49155, nodejs/node#49275, nodejs/node#49161, nodejs/node#49312, nodejs/node#49464)
Appeared test-rackspace-win2019_vs2019-x64-2, test-digitalocean-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53623/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53709/
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 2 (nodejs/node#49150, nodejs/node#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/53627/
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 (nodejs/node#49220, nodejs/node#49274, nodejs/node#49185)
Appeared test-ibm-ubuntu1804-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-digitalocean-ubuntu1804_sharedlibs_container-x64-6, test-digitalocean-ubuntu1804_sharedlibs_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, undefined, test-softlayer-debian10-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-7
First CI https://ci.nodejs.org/job/node-test-pull-request/53678/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53685/
Example 
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from [email protected]: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 ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 3 (nodejs/node#49185, nodejs/node#49220, nodejs/node#49340)
Appeared test-equinix-ubuntu1804_sharedlibs_container-arm64-1, 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/53704/
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 fatal: No rebase in progress?
Type BUILD_FAILURE
Failed PR 3 (nodejs/node#49220, nodejs/node#49400, nodejs/node#49340)
Appeared test-rackspace-debian10-x64-1, test-ibm-ubi81_container-x64-1, test-nearform-macos10.15-x64-1, test-digitalocean-alpine315_container-x64-2, test-digitalocean-alpine318_container-x64-2, 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/53704/
Example 
fatal: No rebase in progress?
Reason sh: line 0: printf: write error: No space left on device
Type BUILD_FAILURE
Failed PR 3 (nodejs/node#49404, nodejs/node#49397, nodejs/node#49391)
Appeared test-nearform-macos10.15-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/53654/
Example 
sh: line 0: printf: write error: No space left on device
Reason ERROR: Step �Publish JUnit test result report� failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#49150, nodejs/node#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 (nodejs/node#49155, nodejs/node#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)

JSTest Failure

Reason sequential/test-http-regr-gh-2928
Type JS_TEST_FAILURE
Failed PR 7 (nodejs/node#49150, nodejs/node#49161, nodejs/node#49185, nodejs/node#49423, nodejs/node#49464, nodejs/node#49424, nodejs/node#49340)
Appeared test-rackspace-win2012r2_vs2015-x64-2, test-digitalocean-freebsd12-x64-1, test-digitalocean-freebsd12-x64-2, test-rackspace-win2012r2_vs2015-x64-1, test-rackspace-win2012r2_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53623/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53704/
Example 
not ok 933 sequential/test-http-regr-gh-2928
  ---
  duration_ms: 538.00100
  severity: fail
  exitcode: 3221226505
  stack: |-
    .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.
  ...
Reason sequential/test-worker-prof
Type JS_TEST_FAILURE
Failed PR 6 (nodejs/node#49161, nodejs/node#49404, nodejs/node#49288, nodejs/node#49185, nodejs/node#49340, nodejs/node#49471)
Appeared test-rackspace-win2022_vs2022-x64-6, test-rackspace-win2019_vs2019-x64-4, test-rackspace-win2022_vs2022-x64-1, test-azure_msft-win2022_vs2019-x64-3, test-rackspace-win2022_vs2022-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/53632/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53707/
Example 
not ok 949 sequential/test-worker-prof
  ---
  duration_ms: 30332.37000
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child exited with signal: {
      error: Error: spawnSync C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe ETIMEDOUT
          at Object.spawnSync (node:internal/child_process:1124:20)
          at spawnSync (node:child_process:876:24)
          at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:52:23)
          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/ru...
Reason parallel/test-blob-file-backed
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#49404, nodejs/node#48655, nodejs/node#49391, nodejs/node#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 node-api/test_threadsafe_function/test
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49341, nodejs/node#49401, nodejs/node#49400)
Appeared test-equinix-ubuntu2004_container-armv7l-2
First CI https://ci.nodejs.org/job/node-test-pull-request/53613/
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-inspector-stop-profile-after-done
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49150, nodejs/node#49413, nodejs/node#49391)
Appeared test-ibm-rhel8-s390x-4, test-ibm-rhel8-s390x-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53627/
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 parallel/test-runner-watch-mode
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49401, nodejs/node#49155, nodejs/node#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-cli-syntax-require
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49150, nodejs/node#49185, nodejs/node#49471)
Appeared test-osuosl-aix72-ppc64_be-3, test-ibm-rhel8-s390x-4, 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/53707/
Example 
not ok 3922 sequential/test-cli-syntax-require
  ---
  duration_ms: 397.25900
  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-aix/nodes/aix72-ppc64/test/sequential/test-cli-syntax-require.js:34:14)
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix72-ppc64/test/common/index.js:474: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 v21.0.0-pre
  ...
Reason sequential/test-single-executable-application-snapshot
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49423, nodejs/node#49413, nodejs/node#49464)
Appeared test-orka-macos11-x64-1, 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/53705/
Example 
not ok 3985 sequential/test-single-executable-application-snapshot
  ---
  duration_ms: 2508.83900
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/fs/utils:352
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, copyfile '/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/out/Release/node' -> '/Users/iojs/node-tmp/.tmp.3987/sea'
        at copyFileSync (node:fs:3011:3)
        at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/sequential/test-single-executable-application-snapshot.js:80:3)
        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 {
      e...
Reason sequential/test-single-executable-application-snapshot-and-code-cache
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49401, nodejs/node#49457, nodejs/node#49464)
Appeared test-orka-macos11-x64-1, test-azure_msft-win2016_vs2017-x64-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/53617/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53705/
Example 
not ok 3986 sequential/test-single-executable-application-snapshot-and-code-cache
  ---
  duration_ms: 1905.79200
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/fs/utils:352
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, copyfile '/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/out/Release/node' -> '/Users/iojs/node-tmp/.tmp.3988/sea'
        at copyFileSync (node:fs:3011:3)
        at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/sequential/test-single-executable-application-snapshot-and-code-cache.js:58:3)
        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/r...
Reason parallel/test-crypto-dh
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49275, nodejs/node#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 (nodejs/node#49275, nodejs/node#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 parallel/test-module-loading-globalpaths
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49424, nodejs/node#49464)
Appeared test-orka-macos11-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53703/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53709/
Example 
not ok 1836 parallel/test-module-loading-globalpaths
  ---
  duration_ms: 1696.31500
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/fs/utils:352
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, copyfile '/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/out/Release/node' -> '/Users/iojs/node-tmp/.tmp.1835/install/bin/node'
        at Object.copyFileSync (node:fs:3011:3)
        at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/parallel/test-module-loading-globalpaths.js:32:6)
        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 {
      errno: -2...
Reason parallel/test-runner-output
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49391, nodejs/node#49463)
Appeared test-ibm-rhel8-x64-2, test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53654/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53702/
Example 
not ok 2585 parallel/test-runner-output
  ---
  duration_ms: 3662.94500
  severity: fail
  exitcode: 1
  stack: |-
    TAP version 13
    # Subtest: test runner output
        # Subtest: test-runner/output/abort.js
        ok 1 - test-runner/output/abort.js
          ---
          duration_ms: 1835.387789
          ...
Reason pummel/test-heapdump-shadow-realm
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49397, nodejs/node#49185)
Appeared test-rackspace-debian10-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/53646/
Last CI https://ci.nodejs.org/job/node-test-pull-request/53685/
Example 
not ok 3618 pummel/test-heapdump-shadow-realm
  ---
  duration_ms: 53305.11600
  severity: crashed
  exitcode: -6
  stack: |-
    
    <--- Last few GCs --->
     =[971:0x5557917a08c0]    50651 ms: Mark-Compact (reduce) 996.1 (1012.6) -> 995.5 (1013.1) MB, 1159.37 / 0.00 ms  (+ 114.4 ms in 17 steps since start of marking, biggest step 18.1 ms, walltime since start of marking 1290 ms) (average mu = 0.267, current mu [971:0x5557917a08c0]    52842 ms: Mark-Compact (reduce) 995.7 (1013.1) -> 995.6 (1013.3) MB, 1945.78 / 0.00 ms  (+ 3.7 ms in 2 steps since start of marking, biggest step 2.0 ms, walltime since start of marking 1958 ms) (average mu = 0.180, current mu = 0.
    
    <--- JS stacktrace --->
    
    FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
     1: 0x55578c8a3580 node::Abort() [out/Release/node]
     2: 0x55578c77f55b  [out/Release/node]
     3: 0x55578cac1e70 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [out/Release/no...

Progress

  • Build timed out (after 60 minutes). Marking the build as failed. (6)
  • Value of: (!expectation.read_expected) (2)
  • ERROR: Error fetching remote repo 'origin' (3)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (3)
  • fatal: No rebase in progress? (3)
  • sh: line 0: printf: write error: No space left on device (3)
  • 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)
  • sequential/test-http-regr-gh-2928 (7)
  • sequential/test-worker-prof (6)
  • parallel/test-blob-file-backed (4)
  • node-api/test_threadsafe_function/test (3)
  • parallel/test-inspector-stop-profile-after-done (3)
  • parallel/test-runner-watch-mode (3)
  • sequential/test-cli-syntax-require (3)
  • sequential/test-single-executable-application-snapshot (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)
  • parallel/test-module-loading-globalpaths (2)
  • parallel/test-runner-output (2)
  • pummel/test-heapdump-shadow-realm (2)
@joyeecheung joyeecheung mentioned this issue Sep 4, 2023
Merged
nodejs-github-bot pushed a commit to nodejs/node that referenced this issue Sep 7, 2023
@joyeecheung
test: split test-crypto-dh to avoid timeout on slow machines in the CI
e0fb3f7 
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was
previously timing out in CI (took more than 2 minutes) so should see
a bigger gap in the CI.

PR-URL: #49492
Refs: #49202
Refs: nodejs/reliability#655
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Chemi Atlow <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
ruyadorno pushed a commit to nodejs/node that referenced this issue Sep 28, 2023
@joyeecheung @ruyadorno
test: split test-crypto-dh to avoid timeout on slow machines in the CI
f214428 
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was
previously timing out in CI (took more than 2 minutes) so should see
a bigger gap in the CI.

PR-URL: #49492
Refs: #49202
Refs: nodejs/reliability#655
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Chemi Atlow <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
alexfernandez pushed a commit to alexfernandez/node that referenced this issue Nov 1, 2023
@joyeecheung @alexfernandez
test: split test-crypto-dh to avoid timeout on slow machines in the CI
aff6eb8 
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was
previously timing out in CI (took more than 2 minutes) so should see
a bigger gap in the CI.

PR-URL: nodejs#49492
Refs: nodejs#49202
Refs: nodejs/reliability#655
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Chemi Atlow <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
targos pushed a commit to nodejs/node that referenced this issue Nov 15, 2023
@joyeecheung @targos
test: split test-crypto-dh to avoid timeout on slow machines in the CI
65b41eb 
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was
previously timing out in CI (took more than 2 minutes) so should see
a bigger gap in the CI.

PR-URL: #49492
Refs: #49202
Refs: nodejs/reliability#655
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Chemi Atlow <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
sercher added a commit to sercher/graaljs that referenced this issue Apr 25, 2024
@sercher
test: split test-crypto-dh to avoid timeout on slow machines
134d45b 
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was
previously timing out in CI (took more than 2 minutes) so should see
a bigger gap in the CI.

PR-URL: nodejs/node#49492
Refs: nodejs/node#49202
Refs: nodejs/reliability#655
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Chemi Atlow <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
sercher added a commit to sercher/graaljs that referenced this issue Apr 25, 2024
@sercher
test: split test-crypto-dh to avoid timeout on slow machines
92eabdb 
Locally this speeds up running test-crypto-dh* from 7s to 2s. This was
previously timing out in CI (took more than 2 minutes) so should see
a bigger gap in the CI.

PR-URL: nodejs/node#49492
Refs: nodejs/node#49202
Refs: nodejs/reliability#655
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Chemi Atlow <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants