Skip to content

CI Reliability 2022-09-05 #368

New issue
New issue
Open
Open
CI Reliability 2022-09-05#368
@github-actions

Description

@github-actions
github-actions
opened on Sep 5, 2022

Failures in node-test-pull-request/46317 to node-test-pull-request/46413 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-09-05 00:17 0 2 36 9 53 2.20%

Jenkins Failure

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 12 (nodejs/node#44450, nodejs/node#44410, nodejs/node#44362, nodejs/node#44469, nodejs/node#44470, nodejs/node#44468, nodejs/node#44473, nodejs/node#44366, nodejs/node#44379, nodejs/node#44327, nodejs/node#44480, nodejs/node#44479)
Appeared test-equinix-ubuntu2004_container-armv7l-2, test-digitalocean-freebsd12-x64-2, test-azure_msft-win10_vs2019-x64-2, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46321/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46413/
Example 
java.io.IOException: Backing channel 'JNLP4-connect connection from 145.40.99.31/145.40.99.31:47254' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy87.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1215)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1207)

Git Failure

Reason ERROR: Error fetching remote repo 'origin'
Type GIT_FAILURE
Failed PR 2 (nodejs/node#44473, nodejs/node#44366)
Appeared test-osuosl-rhel8-ppc64_le-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46375/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46381/
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:1244)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1308)
	at hudson.scm.SCM.checkout(SCM.java:540)

Build Failure

Reason ERROR: Build step failed with exception
Type BUILD_FAILURE
Failed PR 4 (nodejs/node#44358, nodejs/node#44500, nodejs/node#44509, nodejs/node#44366)
Appeared test-equinix-ubuntu2004_container-armv7l-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46409/
Example 
ERROR: Build step failed with exception
java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[test-equinix-ubuntu2004_container-armv7l-2] which is computer hudson.slaves.SlaveComputer@4a73d9df and has channel null
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:114)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92)
	at org.jenkinsci.plugins.postbuildscript.processor.Processor.processBuildSteps(Processor.java:180)
	at org.jenkinsci.plugins.postbuildscript.processor.Processor.processScripts(Processor.java:91)
Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 4 (nodejs/node#44327, nodejs/node#44376, nodejs/node#44418, nodejs/node#44412)
Appeared test-equinix-ubuntu1804_sharedlibs_container-arm64-3, test-osuosl-aix72-ppc64_be-3, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian10_container-armv7l-2, test-equinix-debian10_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46331/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46404/
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 Failed to trigger node-test-commit
Type BUILD_FAILURE
Failed PR 4 (, nodejs/node#44427, nodejs/node#44436, nodejs/node#44473)
Appeared test-packetnet-ubuntu1804-x64-2, test-ibm-ubuntu1804-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46322/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46365/
Example 
Failed to trigger node-test-commit
Reason ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#44475, nodejs/node#44498)
Appeared test-equinix-ubuntu2004_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46372/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46399/
Example 
ERROR: Step ?Publish JUnit test result report? failed: no workspace for node-test-commit-arm/nodes=ubuntu2004-armv7l #43539
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

JSTest Failure

Reason sequential/test-heap-prof
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44398, nodejs/node#44450, nodejs/node#44429, nodejs/node#44362, nodejs/node#44434)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46317/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46345/
Example 
not ok 870 sequential/test-heap-prof
  ---
  duration_ms: 120.834
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...
Reason wpt/test-webcrypto
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44467, nodejs/node#44468, nodejs/node#44486, nodejs/node#44500, nodejs/node#44327)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46356/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46401/
Example 
not ok 898 wpt/test-webcrypto
  ---
  duration_ms: 720.980
  severity: fail
  exitcode: 1
  stack: |-
    timeout
    ---- algorithm-discards-context.https.window.js ----
    [SKIPPED] Not relevant in Node.js context
    ---- historical.any.js ----
    [SKIPPED] Not relevant in Node.js context
    ---- idlharness.https.any.js ----
    [SKIPPED] Various non-IDL-compliant things
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] setup - define tests
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 good parameters
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 mixed case parameters
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 with null length
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 short result
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 non-multiple of 8 bits
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    ...
Reason parallel/test-zlib-unused-weak
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44398, nodejs/node#44450, nodejs/node#44429, nodejs/node#44362)
Appeared test-rackspace-win2012r2_vs2017-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46317/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46337/
Example 
not ok 664 parallel/test-zlib-unused-weak
  ---
  duration_ms: 0.188
  severity: fail
  exitcode: 1
  stack: |-
    assert.js:386
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: Expected after-GC delta 455936 to be less than 5 % of before-GC delta 1612937
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-zlib-unused-weak.js:16:1)
        at Module._compile (internal/modules/cjs/loader.js:999:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
        at Module.load (internal/modules/cjs/loader.js:863:32)
        at Function.Module._load (internal/modules/cjs/loader.js:708:14)
        at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
        at internal/main/run_main_module.js:17:47 {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
  ...
Reason addons/report-fatalerror/test
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44461, nodejs/node#44473)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46354/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46375/
Example 
not ok 3443 addons/report-fatalerror/test
  ---
  duration_ms: 300.74
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...
Reason addons/request-interrupt/test
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44493, nodejs/node#44412)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46390/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46404/
Example 
not ok 3450 addons/request-interrupt/test
  ---
  duration_ms: 300.127
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...
Reason parallel/test-child-process-exec-timeout
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44362, nodejs/node#44398)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46337/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46353/
Example 
not ok 105 parallel/test-child-process-exec-timeout
  ---
  duration_ms: 12.56
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-exec-timeout.js:20
      assert.strictEqual(err.killed, true);
                             ^
    
    TypeError: Cannot read properties of null (reading 'killed')
        at C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-exec-timeout.js:20:26
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:444:15
        at ChildProcess.exithandler (node:child_process:404:7)
        at ChildProcess.emit (node:events:513:28)
        at maybeClose (node:internal/child_process:1091:16)
        at ChildProcess._handle.onexit (node:internal/child_process:302:5)
    
    Node.js v19.0.0-pre
  ...
Reason parallel/test-http2-client-upload-reject
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44418, nodejs/node#44469)
Appeared test-orka-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46318/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46360/
Example 
not ok 1301 parallel/test-http2-client-upload-reject
  ---
  duration_ms: 0.309
  severity: fail
  exitcode: 1
  stack: |-
    node:events:491
          throw er; // Unhandled 'error' event
          ^
    
    Error: read ECONNRESET
        at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
    Emitted 'error' event on ClientHttp2Stream instance at:
        at ClientHttp2Stream.onerror (node:internal/streams/readable:785:14)
        at ClientHttp2Stream.emit (node:events:513:28)
        at emitErrorNT (node:internal/streams/destroy:151:8)
        at emitErrorCloseNT (node:internal/streams/destroy:116:3)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
      errno: -54,
      code: 'ECONNRESET',
      syscall: 'read'
    }
    
    Node.js v19.0.0-pre
  ...
Reason parallel/test-vm-timeout-escape-promise-2
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44450, nodejs/node#44434)
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/46329/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46366/
Example 
not ok 755 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 0.374
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:20
          throw new Error(
                ^
    
    Error: escaped timeout at 100 milliseconds!
        at loop (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:20:13)
        at evalmachine.<anonymous>:1:30
        at Script.runInContext (node:vm:141:12)
        at Script.runInNewContext (node:vm:146:17)
        at Object.runInNewContext (node:vm:306:38)
        at assert.throws.code (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:27:6)
        at getActual (node:assert:757:5)
        at Function.throws (node:assert:903:24)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:26:8)
       ...
Reason parallel/test-worker-heap-snapshot
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44434, nodejs/node#44366)
Appeared test-rackspace-win2012r2_vs2019-x64-3, test-rackspace-win2012r2_vs2019-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46366/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46409/
Example 
not ok 804 parallel/test-worker-heap-snapshot
  ---
  duration_ms: 1.287
  severity: fail
  exitcode: 134
  stack: |-
    FATAL ERROR: HandleScope::HandleScope Entering the V8 API without proper locking in place
  ...
Reason sequential/test-child-process-execsync
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44358, nodejs/node#44500)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46396/
Example 
not ok 693 sequential/test-child-process-execsync
  ---
  duration_ms: 3.881
  severity: fail
  exitcode: 1
  stack: |-
    assert.js:386
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
    
      assert(end < SLEEP)
    
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-child-process-execsync.js:61:3)
        at Module._compile (internal/modules/cjs/loader.js:999:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
        at Module.load (internal/modules/cjs/loader.js:863:32)
        at Function.Module._load (internal/modules/cjs/loader.js:708:14)
        at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
        at internal/main/run_main_module.js:17:47 {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
  ...
Reason sequential/test-diagnostic-dir-cpu-prof
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44450, nodejs/node#44412)
Appeared test-ibm-rhel7-s390x-3, test-equinix-ubuntu1804_sharedlibs_container-arm64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46335/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46392/
Example 
not ok 2942 sequential/test-diagnostic-dir-cpu-prof
  ---
  duration_ms: 0.315
  severity: fail
  exitcode: 1
  stack: |-
    Dispatching message { "id": 1, "method": "Profiler.enable" }
    Receive CPU profile message
    {"id":1,"result":{}}
    Dispatching message { "id": 2, "method": "Profiler.start" }
    Receive CPU profile message
    {"id":2,"result":{}}
    Dispatching message { "id": 3, "method": "Profiler.setSamplingInterval", "params": { "interval": 50 } }
    Receive CPU profile message
    {"error":{"code":-32000,"message":"Cannot change sampling interval when profiling."},"id":3}
    EndStartedProfilers
    V8CpuProfilerConnection::End(), ending = false
    Dispatching message { "id": 4, "method": "Profiler.stop" }
    Receive CPU profile message
    Writing profile response (id = 4)
    Written result to /home/iojs/node-tmp/.tmp.0/prof/CPU.20220902.061102.20881.0.001.cpuprofile
    
    [
      {
        id: 1,
        callFrame: {
          functionName: '(root)',
          scriptId: '0',
   ...

Progress

  • Backing channel 'JNLP4-connect connection from ... is disconnected. (12)
    ERROR: Error fetching remote repo 'origin' (2)
    ERROR: Build step failed with exception (4)
    ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (4)
    Failed to trigger node-test-commit (4)
    ERROR: Step ?Publish JUnit test result report? failed: no workspace for ... (2)
    sequential/test-heap-prof (5)
    wpt/test-webcrypto (5)
    parallel/test-zlib-unused-weak (4)
    addons/report-fatalerror/test (2)
    addons/request-interrupt/test (2)
    parallel/test-child-process-exec-timeout (2)
    parallel/test-http2-client-upload-reject (2)
    parallel/test-vm-timeout-escape-promise-2 (2)
    parallel/test-worker-heap-snapshot (2)
    sequential/test-child-process-execsync (2)
    sequential/test-diagnostic-dir-cpu-prof (2)

Activity

ywave620
mentioned this on Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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

      Participants

      No participants

      Issue actions
        CI Reliability 2022-09-05 · Issue #368 · nodejs/reliability