Skip to content

CI Reliability 2022-08-08 #340

New issue
New issue
Open
Open
CI Reliability 2022-08-08#340
@github-actions

Description

@github-actions
github-actions
opened on Aug 8, 2022

Failures in node-test-pull-request/45809 to node-test-pull-request/45908 that failed more than 2 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
2022-08-08 00:14 0 9 28 5 58 9.47%

Jenkins Failure

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 6 (nodejs/node#44110, nodejs/node#44129, nodejs/node#44102, nodejs/node#44091, nodejs/node#44100, nodejs/node#44016)
Appeared test-digitalocean-freebsd12-x64-2, test-nearform-macos10.15-x64-3, test-nearform-macos11.0-arm64-1, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/45817/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45889/
Example 
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:63447' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
	at com.sun.proxy.$Proxy79.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)
Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 2 (nodejs/node#44080, nodejs/node#44162)
Appeared test-softlayer-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/45812/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45901/
Example 
Build timed out (after 60 minutes). Marking the build as failed.

Git Failure

Build Failure

Reason ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 4 (nodejs/node#44080, nodejs/node#44129, nodejs/node#44132, nodejs/node#44102)
Appeared test-nearform-macos10.15-x64-3, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/45812/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45842/
Example 
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-osx/nodes=osx1015 #46644
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#44132, nodejs/node#44074)
Appeared test-equinix-debian10_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian10_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/45840/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45908/
Example 
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
[PostBuildScript] - [INFO] Executing post build scripts.
[node-test-binary-armv7l] $ /bin/bash -ex /tmp/jenkins16326094327283938115.sh
+ '[' -d .git ']'
+ git clean -fdx

undefined

Reason Unknown
Type undefined
Failed PR 14 (nodejs/node#44090, nodejs/node#44080, nodejs/node#44110, nodejs/node#44101, nodejs/node#44109, nodejs/node#44132, nodejs/node#44102, nodejs/node#43455, nodejs/node#44140, nodejs/node#44163, nodejs/node#44155, nodejs/node#44157, nodejs/node#44149, nodejs/node#44074)
Appeared test-equinix-debian10_container-armv7l-1, test-nearform_arm-win10_vs2019-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/45810/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45908/
Example 
Unknown

JSTest Failure

Reason parallel/test-diagnostics-channel-net
Type JS_TEST_FAILURE
Failed PR 14 (nodejs/node#44080, nodejs/node#44091, nodejs/node#44090, nodejs/node#44048, nodejs/node#44018, nodejs/node#44102, nodejs/node#44140, nodejs/node#43455, nodejs/node#44146, nodejs/node#44139, nodejs/node#44100, nodejs/node#44155, nodejs/node#44141, nodejs/node#44016)
Appeared undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/45809/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45891/
Example 
not ok 653 parallel/test-diagnostics-channel-net
  ---
  duration_ms: 0.335
  severity: fail
  exitcode: 1
  stack: |-
    Mismatched <anonymous> function calls. Expected exactly 1, actual 0.
  ...
Reason parallel/test-heapsnapshot-near-heap-limit-worker
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44090, nodejs/node#44110, nodejs/node#44109, nodejs/node#44102)
Appeared test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-6, test-rackspace-win2012r2_vs2019-x64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/45810/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45842/
Example 
not ok 328 parallel/test-heapsnapshot-near-heap-limit-worker
  ---
  duration_ms: 4.506
  severity: fail
  exitcode: 1
  stack: |-
    
    Invoked NearHeapLimitCallback, processing=false, current_limit=52428800, initial_limit=52428800
    max_young_gen_size=25165824, young_gen_size=0, old_gen_size=51250696, total_size=51250696
    Estimated available memory=6149320704, estimated overhead=25165824
    Start generating Heap.20220804.165945.4268.1.001.heapsnapshot...
    Wrote snapshot to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.291\Heap.20220804.165945.4268.1.001.heapsnapshot
    
    <--- Last few GCs --->
    
    [4268:06503560]     2753 ms: Mark-sweep (reduce) 48.8 (52.8) -> 48.8 (52.8) MB, 6.2 / 0.0 ms  (average mu = 0.333, current mu = -0.150) heap profiler; GC in old space requested
    
    
    <--- JS stacktrace --->
    
    FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
     1: 012FEB2B v8::internal::Heap::PageFlagsAreC...
Reason parallel/test-worker-heap-snapshot
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44080, nodejs/node#44139, nodejs/node#44155)
Appeared test-rackspace-win2012r2_vs2019-x64-4, test-joyent-smartos20-x64-3, test-rackspace-win2012r2_vs2017-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/45815/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45897/
Example 
not ok 790 parallel/test-worker-heap-snapshot
  ---
  duration_ms: 1.412
  severity: fail
  exitcode: 134
  stack: |-
    FATAL ERROR: HandleScope::HandleScope Entering the V8 API without proper locking in place
  ...
Reason parallel/test-crypto-secure-heap
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44090, nodejs/node#44129)
Appeared test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/45813/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45834/
Example 
not ok 451 parallel/test-crypto-secure-heap
  ---
  duration_ms: 0.407
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:1027
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The input did not match the regular expression /--secure-heap must be a power of 2/. Input:
    
    ''
    
        at ChildProcess.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/parallel/test-crypto-secure-heap.js:71:12)
        at ChildProcess.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/common/index.js:420:15)
        at ChildProcess.emit (node:events:513:28)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '',
      expected: /--secure-heap must be a power of 2/,
      operator: 'match'
    }
  ...
Reason parallel/test-debugger-extract-function-name
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44101, nodejs/node#44140)
Appeared test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/45824/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45861/
Example 
not ok 214 parallel/test-debugger-extract-function-name
  ---
  duration_ms: 6.690
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (5000) while waiting for /break (?:on start )?in/i; found: < Debugger listening on ws://127.0.0.1:9229/e480ce69-73fd-48ce-bcb5-7b82c4320235
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    connecting to 127.0.0.1:9229 ...
     ok
    < Debugger attached.
    < 
    
    debug> 
        at Timeout.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84:18)
        at listOnTimeout (node:internal/timers:564:17)
        at process.processTimers (node:internal/timers:507:7)
    
    Node.js v19.0.0-pre
  ...
Reason parallel/test-worker-fshandles-open-close-on-termination
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44101, nodejs/node#44129)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-rackspace-win2012r2_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/45818/
Last CI https://ci.nodejs.org/job/node-test-pull-request/45868/
Example 
not ok 2980 parallel/test-worker-fshandles-open-close-on-termination
  ---
  duration_ms: 120.105
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

Progress

  • Backing channel 'JNLP4-connect connection from ... is disconnected. (6)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (4)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • Unknown (14)
  • parallel/test-diagnostics-channel-net (14)
  • parallel/test-heapsnapshot-near-heap-limit-worker (4)
  • parallel/test-worker-heap-snapshot (3)
  • parallel/test-crypto-secure-heap (2)
  • parallel/test-debugger-extract-function-name (2)
  • parallel/test-worker-fshandles-open-close-on-termination (2)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions