CI Reliability 2023-07-07 #610

github-actions · 2023-07-07T00:17:26Z

Failures in node-test-pull-request/52543 to node-test-pull-request/52642 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-07-07 00:17	0	0	40	1	59	0.00%

JSTest Failure

Reason	`pummel/test-net-throttle`
Type	JS_TEST_FAILURE
Failed PR	5 (nodejs/node#48592, nodejs/node#48633, nodejs/node#48596, nodejs/node#48664, nodejs/node#48550)
Appeared	test-digitalocean-freebsd12-x64-1, test-digitalocean-freebsd12-x64-2
First CI	https://ci.nodejs.org/job/node-test-pull-request/52552/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52635/

Example

not ok 3613 pummel/test-net-throttle
  ---
  duration_ms: 442.84700
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    false !== true
    
        at process.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/pummel/test-net-throttle.js:87:10)
        at process.emit (node:events:526:35) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: 'strictEqual'
    }
    
    Node.js v21.0.0-pre
  ...

Reason	`parallel/test-crypto-dh`
Type	JS_TEST_FAILURE
Failed PR	4 (nodejs/node#48597, nodejs/node#48639, nodejs/node#48596, nodejs/node#39463)
Appeared	test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-6, test-azure_msft-win11_vs2022-arm64-2, test-rackspace-win2012r2_vs2015-x64-2
First CI	https://ci.nodejs.org/job/node-test-pull-request/52558/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52636/

Example

not ok 909 parallel/test-crypto-dh
  ---
  duration_ms: 120092.00000
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...

Reason	`parallel/test-crypto-keygen`
Type	JS_TEST_FAILURE
Failed PR	4 (nodejs/node#48555, nodejs/node#48648, nodejs/node#48551, nodejs/node#39463)
Appeared	test-rackspace-win2012r2_vs2015-x64-1, test-rackspace-win2012r2_vs2019-x64-6, test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52577/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52632/

Example

not ok 884 parallel/test-crypto-keygen
  ---
  duration_ms: 120164.99500
  severity: fail
  exitcode: 1
  stack: |-
    timeout
    (node:5972) [DEP0154] DeprecationWarning: "options.hash" is deprecated, use "options.hashAlgorithm" instead.
    (Use `node --trace-deprecation ...` to show where the warning was created)
    (node:5972) [DEP0154] DeprecationWarning: "options.mgf1Hash" is deprecated, use "options.mgf1HashAlgorithm" instead.
    (node:5972) [DEP0154] DeprecationWarning: "options.mgf1Hash" is deprecated, use "options.mgf1HashAlgorithm" instead.
    (node:5972) [DEP0154] DeprecationWarning: "options.hash" is deprecated, use "options.hashAlgorithm" instead.
  ...

Reason	`parallel/test-inspector-debug-end`
Type	JS_TEST_FAILURE
Failed PR	3 (nodejs/node#48606, nodejs/node#39463, nodejs/node#48142)
Appeared	test-ibm-rhel8-s390x-4
First CI	https://ci.nodejs.org/job/node-test-pull-request/52579/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52609/

Example

not ok 3578 parallel/test-inspector-debug-end
  ---
  duration_ms: 120033.84700
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    Test there's no crash stopping server that was not started
    Test there's no crash stopping server without connecting
    [err] Debugger listening on ws://127.0.0.1:37109/8c6434a5-0ef0-4c68-b1e8-6ec6d8d22a53
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    Test there's no crash stopping server after connecting
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:45921/83b0884f-177b-47b6-8049-04acea06cd30
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] 
  ...

Reason	`parallel/test-string-decoder`
Type	JS_TEST_FAILURE
Failed PR	3 (nodejs/node#39463, nodejs/node#48658, nodejs/node#48550)
Appeared	test-azure_msft-win2016_vs2017-x64-6
First CI	https://ci.nodejs.org/job/node-test-pull-request/52640/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52642/

Example

not ok 699 parallel/test-string-decoder
  ---
  duration_ms: 158.00200
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:635
          throw err;
          ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
    + actual - expected
    
    + Comparison {}
    - Comparison {
    -   code: 'ERR_STRING_TOO_LONG'
    - }
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-string-decoder.js:205:10)
        at Module._compile (node:internal/modules/cjs/loader:1233:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1287: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: true,
      code: 'ERR_ASSERTION',
      actual: RangeError: Array buffer allocat...

Reason	`sequential/test-http-regr-gh-2928`
Type	JS_TEST_FAILURE
Failed PR	3 (nodejs/node#48618, nodejs/node#48658, nodejs/node#39463)
Appeared	test-digitalocean-freebsd12-x64-2, test-rackspace-win2012r2_vs2015-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52570/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52639/

Example

not ok 3884 sequential/test-http-regr-gh-2928
  ---
  duration_ms: 120096.58800
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.
  ...

Reason	`sequential/test-single-executable-application-empty`
Type	JS_TEST_FAILURE
Failed PR	3 (nodejs/node#48555, nodejs/node#48660, nodejs/node#48550)
Appeared	test-nearform-macos10.15-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52582/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52642/

Example

not ok 3931 sequential/test-single-executable-application-empty
  ---
  duration_ms: 7416.28300
  severity: fail
  exitcode: 1
  stack: |-
    Wrote single executable preparation blob to sea-prep.blob
    error: /Library/Developer/CommandLineTools/usr/bin/codesign_allocate: can't write output file: /Users/iojs/node-tmp/.tmp.3930/sea.cstemp (No space left on device)
    /Users/iojs/node-tmp/.tmp.3930/sea: the codesign_allocate helper tool cannot be found or used
    node:child_process:926
        throw err;
        ^
    
    Error: Command failed: codesign --sign - /Users/iojs/node-tmp/.tmp.3930/sea
    error: /Library/Developer/CommandLineTools/usr/bin/codesign_allocate: can't write output file: /Users/iojs/node-tmp/.tmp.3930/sea.cstemp (No space left on device)
    /Users/iojs/node-tmp/.tmp.3930/sea: the codesign_allocate helper tool cannot be found or used
    
        at checkExecSyncError (node:child_process:887:11)
        at execFileSync (node:child_process:923:15)
        at injectAndCodeSign (/Users/...

Reason	`parallel/test-fs-watch-recursive-add-file-to-existing-subfolder`
Type	JS_TEST_FAILURE
Failed PR	2 (nodejs/node#48599, nodejs/node#48658)
Appeared	test-digitalocean-alpine315_container-x64-1, test-ibm-rhel8-s390x-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52560/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52641/

Example

not ok 1369 parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
  ---
  duration_ms: 120086.94600
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

Reason	`parallel/test-tls-ticket-cluster`
Type	JS_TEST_FAILURE
Failed PR	2 (nodejs/node#45704, nodejs/node#39463)
Appeared	test-azure_msft-win2022_vs2019-x64-4, test-rackspace-win2012r2_vs2015-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52622/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52632/

Example

not ok 758 parallel/test-tls-ticket-cluster
  ---
  duration_ms: 691.04700
  severity: fail
  exitcode: 1
  stack: |-
    [primary] got "listening"
    [primary] connecting 64323 session? false
    [primary] got "listening"
    [primary] got "listening"
    [primary] connecting 64323 session? false
    [worker] connection reused? false
    [primary] got "not-reused"
    [primary] connecting 64323 session? true
    [primary] got "listening"
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64323 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64323 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64323 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64323 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 64323 session? true
    [worker] connection reused? tru...

Reason	`pummel/test-fs-readfile-tostring-fail`
Type	JS_TEST_FAILURE
Failed PR	2 (nodejs/node#39463, nodejs/node#48658)
Appeared	test-nearform-macos10.15-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52602/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52641/

Example

not ok 3584 pummel/test-fs-readfile-tostring-fail
  ---
  duration_ms: 67.24900
  severity: fail
  exitcode: 7
  stack: |-
    /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/pummel/test-fs-readfile-tostring-fail.js:77
      throw err;
      ^
    
    AssertionError [ERR_ASSERTION]: ifError got unwanted exception: ENOSPC: no space left on device, write
        at Object.callback (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/pummel/test-fs-readfile-tostring-fail.js:35:37)
        at callback (node:internal/streams/writable:562:21)
        at onwriteError (node:internal/streams/writable:425:3)
        at onwrite (node:internal/streams/writable:467:7)
        at node:internal/fs/streams:439:14
        at FSReqCallback.wrapper [as oncomplete] (node:fs:970:5) {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: [Error: ENOSPC: no space left on device, write] {
        errno: -28,
        code: 'ENOSPC',
        syscall: 'write'
      },
      expec...

Reason	`pummel/test-heapdump-shadow-realm`
Type	JS_TEST_FAILURE
Failed PR	2 (nodejs/node#48633, nodejs/node#48596)
Appeared	test-equinix-ubuntu2004_sharedlibs_container-arm64-5, test-rackspace-fedora32-x64-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-6
First CI	https://ci.nodejs.org/job/node-test-pull-request/52615/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52618/

Example

not ok 3591 pummel/test-heapdump-shadow-realm
  ---
  duration_ms: 3316.90400
  severity: crashed
  exitcode: -6
  stack: |-
    out/Debug/node[943015]: ../src/node_realm.cc:293:virtual void node::PrincipalRealm::set_async_hooks_binding(v8::Local<v8::Object>): Assertion `!(!value.IsEmpty()) || (isolate()->GetCurrentContext() == context())' failed.
     1: 0xaaaacd989ca0 node::DumpBacktrace(_IO_FILE*) [out/Debug/node]
     2: 0xaaaacda9c26c node::Abort() [out/Debug/node]
     3: 0xaaaacda9c340  [out/Debug/node]
     4: 0xaaaacdb93328 node::PrincipalRealm::set_async_hooks_binding(v8::Local<v8::Object>) [out/Debug/node]
     5: 0xaaaacd92f6c4 node::Environment::set_async_hooks_binding(v8::Local<v8::Object>) [out/Debug/node]
     6: 0xaaaacd9224e0 node::AsyncWrap::CreatePerContextProperties(v8::Local<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Context>, void*) [out/Debug/node]
     7: 0xaaaacda3cfe0  [out/Debug/node]
     8: 0xaaaacda3d148 node::binding::GetInternalBinding(v8::FunctionCallbackInfo<v8::Value>...

Reason	`sequential/test-single-executable-application-disable-experimental-sea-warning`
Type	JS_TEST_FAILURE
Failed PR	2 (nodejs/node#39463, nodejs/node#48658)
Appeared	test-nearform-macos10.15-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52602/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52641/

Example

not ok 3930 sequential/test-single-executable-application-disable-experimental-sea-warning
  ---
  duration_ms: 7092.38100
  severity: fail
  exitcode: 1
  stack: |-
    Wrote single executable preparation blob to sea-prep.blob
    error: /Library/Developer/CommandLineTools/usr/bin/codesign_allocate: can't write output file: /Users/iojs/node-tmp/.tmp.3929/sea.cstemp (No space left on device)
    /Users/iojs/node-tmp/.tmp.3929/sea: the codesign_allocate helper tool cannot be found or used
    node:child_process:924
        throw err;
        ^
    
    Error: Command failed: codesign --sign - /Users/iojs/node-tmp/.tmp.3929/sea
    error: /Library/Developer/CommandLineTools/usr/bin/codesign_allocate: can't write output file: /Users/iojs/node-tmp/.tmp.3929/sea.cstemp (No space left on device)
    /Users/iojs/node-tmp/.tmp.3929/sea: the codesign_allocate helper tool cannot be found or used
    
        at checkExecSyncError (node:child_process:885:11)
        at execFileSync (node:child_process:921:15)
        at...

Jenkins Failure

Reason	`Backing channel 'JNLP4-connect connection from ... is disconnected.`
Type	JENKINS_FAILURE
Failed PR	6 (nodejs/node#48597, nodejs/node#48599, nodejs/node#48566, nodejs/node#48564, nodejs/node#48275, nodejs/node#48660)
Appeared	test-rackspace-fedora32-x64-1, test-orka-macos10.15-x64-1, test-orka-macos11-x64-1, test-orka-macos11-x64-2
First CI	https://ci.nodejs.org/job/node-test-pull-request/52558/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52623/

Example

java.io.IOException: Backing channel 'JNLP4-connect connection from 119.9.51.79/119.9.51.79:43464' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy279.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1215)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1207)

Reason	`Build timed out (after 60 minutes). Marking the build as failed.`
Type	JENKINS_FAILURE
Failed PR	2 (nodejs/node#48592, nodejs/node#48608)
Appeared	test-rackspace-win2012r2_vs2019-x64-6
First CI	https://ci.nodejs.org/job/node-test-pull-request/52552/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52567/

Example

Build timed out (after 60 minutes). Marking the build as failed.

CCTest Failure

Reason	`C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)`
Type	CC_TEST_FAILURE
Failed PR	2 (nodejs/node#48630, nodejs/node#47956)
Appeared	test-azure_msft-win2022_vs2019-x64-4, test-azure_msft-win2022_vs2019-x64-2
First CI	https://ci.nodejs.org/job/node-test-pull-request/52580/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52617/

Example

C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)
  Actual: true
Expected: false

[  FAILED  ] InspectorSocketTest.HostIPv6NonRoutable (5001 ms)

Git Failure

Reason	`ERROR: Error fetching remote repo 'origin'`
Type	GIT_FAILURE
Failed PR	2 (nodejs/node#48658, nodejs/node#48550)
Appeared	test-orka-macos11-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52641/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52642/

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:1003)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1245)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1309)
	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	2 (nodejs/node#48414, nodejs/node#48547)
Appeared	test-equinix_mnx-smartos20-x64-3, test-equinix-ubuntu2004_sharedlibs_container-arm64-5, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-equinix-ubuntu2004_container-arm64-2, test-osuosl-ubuntu2004_container-armv7l-1, test-osuosl-aix72-ppc64_be-3
First CI	https://ci.nodejs.org/job/node-test-pull-request/52551/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52555/

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 test report files were found. Configuration error?`
Type	BUILD_FAILURE
Failed PR	2 (nodejs/node#48414, nodejs/node#48547)
Appeared	test-digitalocean-freebsd12-x64-2, test-ibm-rhel8-s390x-4, test-ibm-rhel8-s390x-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52551/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52555/

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 or unexpected token`
Type	BUILD_FAILURE
Failed PR	2 (nodejs/node#48414, nodejs/node#48547)
Appeared	test-nearform-macos10.15-x64-3, test-orka-macos11-x64-2, test-digitalocean-alpine315_container-x64-2, test-digitalocean-alpine318_container-x64-1, test-rackspace-debian10-x64-1, test-digitalocean-fedora32-x64-1, test-digitalocean-fedora34-x64-1, test-ibm-rhel8-x64-1, test-equinix_mnx-ubuntu1804-x64-1, test-ibm-ubi81_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-8, test-digitalocean-ubuntu1804_sharedlibs_container-x64-10, test-digitalocean-ubuntu1804_sharedlibs_container-x64-6, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-digitalocean-ubuntu1804_sharedlibs_container-x64-5, test-nearform-macos11.0-arm64-1, test-osuosl-rhel8-ppc64_le-4, test-rackspace-win2012r2_vs2019-x64-2, test-rackspace-win2012r2_vs2019-x64-6, test-equinix-ubuntu2004_container-armv7l-1, undefined, test-nearform-macos10.15-x64-1, test-orka-macos11-x64-1, test-osuosl-rhel8-ppc64_le-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/52551/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52555/

Example

Error: Invalid or unexpected token

make[2]: *** [/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/out/Release/obj/gen/node_snapshot.cc] Error 1
rm f9762331d7df19c05986500e4508659a0d607148.intermediate dd8eed00d10ee950b0f3f5853c04c8f20896e9b6.intermediate 79374afa39705ee6adcee5d937fc17b6e7b40b46.intermediate 937da630c0facf199b9ed32a729c46d172d05b74.intermediate
make[1]: *** [node] Error 2
make: *** [build-ci] Error 2

Reason	`fatal: No rebase in progress?`
Type	BUILD_FAILURE
Failed PR	2 (nodejs/node#48551, nodejs/node#39463)
Appeared	test-orka-macos11-x64-2
First CI	https://ci.nodejs.org/job/node-test-pull-request/52610/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/52639/

Example

fatal: No rebase in progress?

Progress

The text was updated successfully, but these errors were encountered:

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CI Reliability 2023-07-07 #610

CI Reliability 2023-07-07 #610

github-actions bot commented Jul 7, 2023

CI Reliability 2023-07-07 #610

CI Reliability 2023-07-07 #610

Comments

github-actions bot commented Jul 7, 2023

JSTest Failure

Jenkins Failure

CCTest Failure

Git Failure

Build Failure

Progress