nodejs / nodejs/reliability

CI Reliability 2024-05-05

Offen
#855 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/58836 to node-test-pull-request/58933 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-05-05 00:08 1 3 13 17 66 3.66%
JSTest Failure
Reason parallel/test-net-write-fully-async-buffer
Type JS_TEST_FAILURE
Failed PR 7 (https://github.com/nodejs/node/pull/52768/, https://github.com/nodejs/node/pull/52781/, https://github.com/nodejs/node/pull/52794/, https://github.com/nodejs/node/pull/52802/, https://github.com/nodejs/node/pull/52811/, https://github.com/nodejs/node/pull/31137/, https://github.com/nodejs/node/pull/51657/)
Appeared test-equinix-rhel8_container-arm64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-4, test-equinix-rhel8_container-arm64-1, test-digitalocean-ubi81_container-x64-1, test-equinix-ubuntu2004_container-arm64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-6
First CI https://ci.nodejs.org/job/node-test-pull-request/58844/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58898/
Example
not ok 3974 parallel/test-net-write-fully-async-buffer
  ---
  duration_ms: 360116.47600
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason benchmark/test-benchmark-crypto
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/52811/, https://github.com/nodejs/node/pull/52821/, https://github.com/nodejs/node/pull/52215/, https://github.com/nodejs/node/pull/52147/, https://github.com/nodejs/node/pull/45427/)
Appeared test-digitalocean-fedora37-x64-1, test-ibm-ubuntu2204-x64-1, test-ibm-alpine319_container-x64-1, test-equinix-rhel8_container-arm64-2, test-ibm-ubi81_container-x64-1, test-rackspace-win2022_vs2022-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/58879/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58921/
Example
not ok 4011 benchmark/test-benchmark-crypto
  ---
  duration_ms: 2411.31700
  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/benchmark/crypto/timingSafeEqual.js:21:10)
        at /home/iojs/build/workspace/node-test-commit-linux/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/test/common/benchmark.js:28:12)
        a...

Reason parallel/test-http2-large-write-multiple-requests
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/52781/, https://github.com/nodejs/node/pull/52760/, https://github.com/nodejs/node/pull/52810/, https://github.com/nodejs/node/pull/52646/, https://github.com/nodejs/node/pull/52347/)
Appeared test-digitalocean-alpine318_container-x64-1, test-ibm-rhel8-x64-2, test-digitalocean-ubuntu2204_sharedlibs_container-x64-5, test-azure_msft-win11_vs2022-x64-2, test-ibm-rhel8-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58842/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58915/
Example
not ok 2501 parallel/test-http2-large-write-multiple-requests
  ---
  duration_ms: 120036.28900
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    server sends content 1
    server sends content 2
    server sends content 3
    server sends content 4
    server sends content 5
    server sends content 6
    server sends content 7
    server sends content 8
    server sends content 9
    server sends content 10
    server sends content 11
    server sends content 12
    server sends content 13
    server sends content 14
    server sends content 15
    server sends content 16
    server sends content 17
    server sends content 18
    server sends content 19
    server sends content 20
    server sends content 21
    server sends content 22
    server sends content 23
    server sends content 24
    server sends content 25
    server sends content 26
    server sends content 27
    server sends content 28
    server sends content 29
    server sends content 30
    server sends content 31
    server s...

Reason parallel/test-pipe-file-to-http
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/52734/, https://github.com/nodejs/node/pull/52791/, https://github.com/nodejs/node/pull/51050/, https://github.com/nodejs/node/pull/52821/, https://github.com/nodejs/node/pull/52702/)
Appeared test-equinix-debian11_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-2, test-equinix-debian11_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58884/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58914/
Example
not ok 3831 parallel/test-pipe-file-to-http
  ---
  duration_ms: 360019.94500
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-stream-readable-unpipe-resume
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/31137/, https://github.com/nodejs/node/pull/52781/, https://github.com/nodejs/node/pull/51250/, https://github.com/nodejs/node/pull/52347/, https://github.com/nodejs/node/pull/52791/)
Appeared test-ibm-ubuntu2204_sharedlibs_container-x64-2, test-ibm-ubuntu2204-x64-1, test-ibm-ubi81_container-x64-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-6, test-digitalocean-ubuntu2204_sharedlibs_container-x64-3, test-equinix-ubuntu2004_container-arm64-2, test-equinix-rhel8_container-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58895/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58933/
Example
not ok 3784 parallel/test-stream-readable-unpipe-resume
  ---
  duration_ms: 120012.59300
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-runner-output
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/52213/, https://github.com/nodejs/node/pull/52793/, https://github.com/nodejs/node/pull/52802/, https://github.com/nodejs/node/pull/52810/)
Appeared test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win11_vs2022-x64-1, test-rackspace-win2016_vs2015-x64-1, test-rackspace-win2019_vs2019-x64-3, test-rackspace-win2022_vs2022-x64-3, test-azure_msft-win11_vs2022-arm64-2, test-azure_msft-win10_vs2019-x64-3, test-rackspace-win2019_vs2019-x64-2, test-rackspace-win2022_vs2022-x64-2, test-azure_msft-win11_vs2022-arm64-1, test-azure_msft-win2016_vs2017-x64-2, test-rackspace-win2022_vs2022-x64-6, test-azure_msft-win11_vs2022-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/58861/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58883/
Example
not ok 671 parallel/test-runner-output
  ---
  duration_ms: 5884.72800
  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: 2062.3982
          ...


Reason parallel/test-blob-file-backed
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/52744/, https://github.com/nodejs/node/pull/52793/, https://github.com/nodejs/node/pull/52347/)
Appeared test-ibm-ubuntu2204_sharedlibs_container-x64-2, test-digitalocean-ubuntu2204_sharedlibs_container-x64-6, test-ibm-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58860/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58915/
Example
not ok 377 parallel/test-blob-file-backed
  ---
  duration_ms: 173.65600
  severity: fail
  exitcode: 1
  stack: |-
    
    node:internal/blob:355
                  const error = lazyDOMException('The blob could not be read', 'NotReadableError');
                                ^
    DOMException [NotReadableError]: The blob could not be read
        at BlobReader.<anonymous> (node:internal/blob:355:29)
    
    Node.js v23.0.0-pre
  ...


Reason parallel/test-performance-function
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/52702/, https://github.com/nodejs/node/pull/52347/, https://github.com/nodejs/node/pull/52791/)
Appeared test-ibm-rhel8-x64-1, test-ibm-ubuntu2204-x64-1, test-ibm-rhel8-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/58893/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58932/
Example
not ok 2382 parallel/test-performance-function
  ---
  duration_ms: 254.95800
  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:540:9)
        at process.processTimers (node:internal/timers:514:7) {
      code: 'ERR_OUT_OF_RANGE'
    }
    
    Node.js v23.0.0-pre
  ...


Reason parallel/test-cli-node-options
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/52760/, https://github.com/nodejs/node/pull/52793/)
Appeared test-rackspace-win2022_vs2022-x64-4, test-azure_msft-win2016_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58853/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58868/
Example
not ok 122 parallel/test-cli-node-options
  ---
  duration_ms: 1573.02300
  severity: crashed
  exitcode: 2147483651
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.124
    Files blocking: [ 'node_trace.1.log' ]
    
    node:internal/child_process:421
        throw new ErrnoException(err, 'spawn');
        ^
    
    Error: spawn UNKNOWN
        at ChildProcess.spawn (node:internal/child_process:421:11)
        at spawn (node:child_process:761:9)
        at execFile (node:child_process:351:17)
        at expect (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-cli-node-options.js:119:3)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-cli-node-options.js:76:1)
        at Module._compile (node:internal/modules/cjs/loader:1358:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
        at Module.load (node:internal/modules/cjs/loader:1208:32)
        at Mo...

Reason sequential/test-single-executable-application-snapshot-and-code-cache
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/52819/, https://github.com/nodejs/node/pull/52791/)
Appeared test-digitalocean-ubuntu2204_sharedlibs_container-x64-6, test-softlayer-debian12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58894/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58933/
Example
not ok 4187 sequential/test-single-executable-application-snapshot-and-code-cache
  ---
  duration_ms: 12153.52300
  severity: fail
  exitcode: 1
  stack: |-
    Copied /home/iojs/build/workspace/node-test-commit-linux-containered/out/Release/node to /home/iojs/node-tmp/.tmp.4186/sea
    Injected /home/iojs/node-tmp/.tmp.4186/sea-prep.blob into /home/iojs/node-tmp/.tmp.4186/sea
    [process 259139]: --- stderr ---
    Found SEA blob 0x558f4ad90080, size=4480889
    Found SEA resource 0x558f4ad90080, size=4480889
    Read<uint32_t>()(4-byte), count=1: { 21223968 }, read 4 bytes
    Read SEA magic 143da20
    Read<uint32_t>()(4-byte), count=1: { 6 }, read 4 bytes
    Read SEA flags 6
    Read<uint64_t>()(8-byte), count=1: { 11 }, read 8 bytes
    ReadStringView(), length=11: 0x558f4ad90090, read 11 bytes, content: snapshot.js
    Read SEA code path 0x558f4ad90090, size=11
    Read<uint64_t>()(8-byte), count=1: { 4480854 }, read 8 bytes
    ReadStringView(), length=4480854: 0x558f4ad900a3, read 4480854 bytes
   ...

Reason wpt/test-compression
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/52810/, https://github.com/nodejs/node/pull/52347/)
Appeared test-digitalocean-ubuntu2204_sharedlibs_container-x64-4, test-ibm-ubuntu2204_sharedlibs_container-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/58880/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58911/
Example
not ok 4074 wpt/test-compression
  ---
  duration_ms: 1440092.45800
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    [SKIPPED] compression-bad-chunks.tentative.any.js: Execution "hangs", ArrayBuffer and TypedArray is not accepted and throws, instead of rejects during writer.write
    [SKIPPED] decompression-bad-chunks.tentative.any.js: Execution "hangs", ArrayBuffer and TypedArray is not accepted and throws, instead of rejects during writer.write
    [SKIPPED] decompression-buffersource.tentative.any.js: ArrayBuffer and TypedArray is not accepted and throws, instead of rejects during writer.write
    [SKIPPED] idlharness-shadowrealm.window.js: ShadowRealm support is not enabled
    [SKIPPED] third_party/pako/pako_inflate.min.js: This is not a test file.
    [PASS] "a" should cause the constructor to throw
    [PASS] no input should cause the constructor to throw
    [PASS] non-string input should cause the constructor to throw
    [PASS] "a" should cause the constructor to throw
    [PASS] no inpu...

Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/52672/, https://github.com/nodejs/node/pull/52821/, https://github.com/nodejs/node/pull/45427/)
Appeared test-digitalocean-ubuntu2204-x64-2, test-rackspace-fedora32-x64-1, undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/58910/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58931/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 167.99.124.188/167.99.124.188:58764' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy181.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1212)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1204)

Git Failure
Build Failure
Reason error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
Type BUILD_FAILURE
Failed PR 14 (https://github.com/nodejs/node/pull/52760/, https://github.com/nodejs/node/pull/52744/, https://github.com/nodejs/node/pull/52781/, https://github.com/nodejs/node/pull/52646/, https://github.com/nodejs/node/pull/52794/, https://github.com/nodejs/node/pull/52802/, https://github.com/nodejs/node/pull/52810/, https://github.com/nodejs/node/pull/52766/, https://github.com/nodejs/node/pull/52701/, https://github.com/nodejs/node/pull/52702/, https://github.com/nodejs/node/pull/52347/, https://github.com/nodejs/node/pull/45427/, https://github.com/nodejs/node/pull/52734/, https://github.com/nodejs/node/pull/52828/)
Appeared test-rackspace-win2022_vs2022-x64-1, test-rackspace-win2022_vs2022-x64-6, test-rackspace-win2022_vs2022-x64-5, test-rackspace-win2022_vs2022-x64-2, test-rackspace-win2022_vs2022-x64-4, test-rackspace-win2022_vs2022-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/58836/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58929/
Example
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(588,5): error MSB6006: "clcache_main.exe" exited with code 1. [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
  object-fromentries-tq-csa.cc
  object-tq-csa.cc
  number-tq-csa.cc

Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 9 (https://github.com/nodejs/node/pull/52794/, https://github.com/nodejs/node/pull/52811/, https://github.com/nodejs/node/pull/52734/, https://github.com/nodejs/node/pull/52793/, https://github.com/nodejs/node/pull/31137/, https://github.com/nodejs/node/pull/51657/, https://github.com/nodejs/node/pull/52781/, https://github.com/nodejs/node/pull/52766/, https://github.com/nodejs/node/pull/52821/)
Appeared test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-equinix-debian11_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-2, test-osuosl-debian11_container-armv7l-1, test-equinix-ubuntu1804_container-arm64-2, test-osuosl-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58869/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58913/
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 ‘Record fingerprints of files to track usage’ failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/52802/, https://github.com/nodejs/node/pull/52791/, https://github.com/nodejs/node/pull/52766/, https://github.com/nodejs/node/pull/52347/, https://github.com/nodejs/node/pull/45427/)
Appeared test-rackspace-fedora32-x64-1, test-digitalocean-ubuntu2204-x64-2, test-digitalocean-ubuntu2204-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58878/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58931/
Example
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for node-test-commit-linux/nodes=fedora-last-latest-x64 #57678
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason fatal error: Killed signal terminated program cc1plus
Type BUILD_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/52802/, https://github.com/nodejs/node/pull/52672/, https://github.com/nodejs/node/pull/45427/, https://github.com/nodejs/node/pull/52821/, https://github.com/nodejs/node/pull/52702/)
Appeared test-rackspace-fedora32-x64-1, undefined, test-digitalocean-rhel8_arm_cross_container-x64-1, test-digitalocean-ubuntu2204_sharedlibs_container-x64-9, test-digitalocean-ubuntu2204-x64-2, test-ibm-rhel8_arm_cross_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58872/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58914/
Example
fatal error: Killed signal terminated program cc1plus

Reason fatal: No rebase in progress?
Type BUILD_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/52766/, https://github.com/nodejs/node/pull/52609/, https://github.com/nodejs/node/pull/52701/, https://github.com/nodejs/node/pull/52791/, https://github.com/nodejs/node/pull/52347/)
Appeared test-ibm-ubuntu2204_sharedlibs_container-x64-4, test-digitalocean-ubuntu2204_sharedlibs_container-x64-6, test-digitalocean-ubuntu2204_sharedlibs_container-x64-4, test-ibm-ubuntu2204_sharedlibs_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/58840/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58915/
Example
fatal: No rebase in progress?

Reason error: remote GitHub already exists.
Type BUILD_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/52781/, https://github.com/nodejs/node/pull/52646/, https://github.com/nodejs/node/pull/52810/)
Appeared test-azure_msft-win11_vs2022-x64-1, test-azure_msft-win11_vs2022-arm64-1, test-rackspace-win2022_vs2022-x64-3, test-rackspace-win2019_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/58866/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58909/
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

Reason error C1002: compiler is out of heap space in pass 2 [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/52766/, https://github.com/nodejs/node/pull/52821/)
Appeared test-rackspace-win2022_vs2022-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/58908/
Last CI https://ci.nodejs.org/job/node-test-pull-request/58913/
Example
error C1002: compiler is out of heap space in pass 2 [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
C:\workspace\node-compile-windows\node\deps\v8\src\heap\setup-heap-internal.cc(847): fatal  error C1002: compiler is out of heap space in pass 2 [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
C:\workspace\node-compile-windows\node\deps\v8\src\objects\tagged-impl.h(172): fatal  error C1002: compiler is out of heap space in pass 2 [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
  keyed-store-generic.cc
C:\workspace\node-compile-windows\node\deps\v8\src\ic\keyed-store-generic.cc(1341,1): fatal  error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]

CCTest Failure
Progress
  • parallel/test-net-write-fully-async-buffer (7)
  • benchmark/test-benchmark-crypto (5)
  • parallel/test-http2-large-write-multiple-requests (5)
  • parallel/test-pipe-file-to-http (5)
  • parallel/test-stream-readable-unpipe-resume (5)
  • parallel/test-runner-output (4)
  • parallel/test-blob-file-backed (3)
  • parallel/test-performance-function (3)
  • parallel/test-cli-node-options (2)
  • sequential/test-single-executable-application-snapshot-and-code-cache (2)
  • wpt/test-compression (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
  • error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (14)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (9)
  • ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... (5)
  • fatal error: Killed signal terminated program cc1plus (5)
  • fatal: No rebase in progress? (5)
  • error: remote GitHub already exists. (3)
  • error C1002: compiler is out of heap space in pass 2 [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (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 CI-Links und den genannten Fehlern: parallel/test-net-write-fully-async-buffer, benchmark/test-benchmark-crypto, parallel/test-http2-large-write-multiple-requests, parallel/test-pipe-file-to-http und parallel/test-stream-readable-unpipe-resume. Reproduziere die Fehler in den aufgeführten CI-Umgebungen und verfolge anschließend die relevante Ausgabe des Tests oder Benchmarks. Als erledigt gilt die Aufgabe, wenn die gemeldeten Fehler diagnostiziert sind und in CI nicht mehr auftreten.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
javascript, node.js, shell
Bereich
ci-cd, testing-qa
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.