CI Reliability 2022-09-03

Open
#366 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, node.js, shell

Research direction

Start by reviewing the linked Jenkins runs and the grouped failure categories, then inspect the named test entry points such as test/parallel/test-child-process-exec-timeout.js and sequential/test-heap-prof. Compare the affected CI jobs and reproduce the failures; done means the reported recurring CI failures have been diagnosed and the relevant jobs return successfully.

Written by the indexing model from the issue text.

Description

Failures in node-test-pull-request/46296 to node-test-pull-request/46394 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-03 00:14 0 2 32 9 57 2.20%
Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 10 (https://github.com/nodejs/node/pull/44179/, https://github.com/nodejs/node/pull/44450/, https://github.com/nodejs/node/pull/44410/, https://github.com/nodejs/node/pull/44362/, https://github.com/nodejs/node/pull/44469/, https://github.com/nodejs/node/pull/44470/, https://github.com/nodejs/node/pull/44468/, https://github.com/nodejs/node/pull/44473/, https://github.com/nodejs/node/pull/44366/, https://github.com/nodejs/node/pull/44379/)
Appeared test-digitalocean-freebsd12-x64-2, test-equinix-ubuntu2004_container-armv7l-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/46299/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46383/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:31570' 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 (https://github.com/nodejs/node/pull/44473/, https://github.com/nodejs/node/pull/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 (https://github.com/nodejs/node/pull/44179/, https://github.com/nodejs/node/pull/44379/, https://github.com/nodejs/node/pull/44279/, https://github.com/nodejs/node/pull/44358/)
Appeared test-equinix-ubuntu2004_container-armv7l-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46299/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46350/
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 (https://github.com/nodejs/node/pull/44327/, https://github.com/nodejs/node/pull/44376/, https://github.com/nodejs/node/pull/44412/, https://github.com/nodejs/node/pull/44418/)
Appeared test-equinix-debian10_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian10_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-2, 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-ubuntu1804_sharedlibs_container-arm64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46331/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46394/
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/jenkins7393630640696152272.sh
+ '[' -d .git ']'
+ git clean -fdx

Reason Failed to trigger node-test-commit
Type BUILD_FAILURE
Failed PR 4 (, https://github.com/nodejs/node/pull/44427/, https://github.com/nodejs/node/pull/44436/, https://github.com/nodejs/node/pull/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 Failed to trigger sub builds
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41023/, https://github.com/nodejs/node/pull/43901/)
Appeared undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/46296/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46320/
Example
Failed to trigger sub builds

Reason error: remote GitHub already exists.
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44388/, https://github.com/nodejs/node/pull/44410/)
Appeared test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46312/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46326/
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

JSTest Failure
Reason sequential/test-heap-prof
Type JS_TEST_FAILURE
Failed PR 7 (https://github.com/nodejs/node/pull/44057/, https://github.com/nodejs/node/pull/44380/, https://github.com/nodejs/node/pull/44398/, https://github.com/nodejs/node/pull/44450/, https://github.com/nodejs/node/pull/44429/, https://github.com/nodejs/node/pull/44362/, https://github.com/nodejs/node/pull/44434/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46298/
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 parallel/test-child-process-exec-timeout
Type JS_TEST_FAILURE
Failed PR 6 (https://github.com/nodejs/node/pull/44066/, https://github.com/nodejs/node/pull/44421/, https://github.com/nodejs/node/pull/44380/, https://github.com/nodejs/node/pull/44327/, https://github.com/nodejs/node/pull/44362/, https://github.com/nodejs/node/pull/44398/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46302/
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-vm-timeout-escape-promise-2
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/44057/, https://github.com/nodejs/node/pull/44327/, https://github.com/nodejs/node/pull/44450/, https://github.com/nodejs/node/pull/44434/)
Appeared test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46298/
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-zlib-unused-weak
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/44398/, https://github.com/nodejs/node/pull/44450/, https://github.com/nodejs/node/pull/44429/, https://github.com/nodejs/node/pull/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 wpt/test-webcrypto
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/44467/, https://github.com/nodejs/node/pull/44468/, https://github.com/nodejs/node/pull/44486/)
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/46384/
Example
not ok 898 wpt/test-webcrypto
  ---
  duration_ms: 720.287
  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 addons/report-fatalerror/test
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44461/, https://github.com/nodejs/node/pull/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 parallel/test-heapsnapshot-near-heap-limit-worker
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44327/, https://github.com/nodejs/node/pull/44450/)
Appeared test-rackspace-win2012r2_vs2015-x64-2, test-rackspace-win2012r2_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46313/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46321/
Example
not ok 323 parallel/test-heapsnapshot-near-heap-limit-worker
  ---
  duration_ms: 4.90
  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=51508936, total_size=51508936
    Estimated available memory=5794344960, estimated overhead=25165824
    Start generating Heap.20220830.163416.4460.1.001.heapsnapshot...
    Wrote snapshot to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.292\Heap.20220830.163416.4460.1.001.heapsnapshot
    
    <--- Last few GCs --->
    
    [4460:0694CAE0]     2487 ms: Mark-sweep (reduce) 49.1 (52.8) -> 49.1 (52.8) MB, 7.8 / 0.0 ms  (average mu = 0.313, current mu = -0.114) 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: 019F31CB v8::internal::Heap::PageFlagsAreCo...

Reason parallel/test-http2-client-upload-reject
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44418/, https://github.com/nodejs/node/pull/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-inspector-esm
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44022/, https://github.com/nodejs/node/pull/44379/)
Appeared test-ibm-rhel8-s390x-4, test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46300/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46303/
Example
not ok 1782 parallel/test-inspector-esm
  ---
  duration_ms: 15.689
  severity: fail
  exitcode: 1
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:41069/96d81102-2d3e-44b7-a6d7-424a939617bb
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [test] Verifying debugger stops on start (--inspect-brk option)
    [err] Debugger attached.
    [err] 
    Timed out waiting for matching notification (break on file:///home/iojs/build/workspace/node-test-commit-linuxone/test/fixtures/es-modules/message.mjs:0)
    1
  ...


Reason sequential/test-child-process-execsync
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44392/, https://github.com/nodejs/node/pull/44358/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46305/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Example
not ok 846 sequential/test-child-process-execsync
  ---
  duration_ms: 6.106
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:400
        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:62:3)
        at Module._compile (node:internal/modules/cjs/loader:1119:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1173:10)
        at Module.load (node:internal/modules/cjs/loader:997:32)
        at Module._load (node:internal/modules/cjs/loader:838:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
        at node:internal/main/run_main_module:18:47 {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v18.8.1-pre
  ...


Reason sequential/test-debugger-auto-resume
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44392/, https://github.com/nodejs/node/pull/44358/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46305/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Example
not ok 852 sequential/test-debugger-auto-resume
  ---
  duration_ms: 10.863
  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: 
        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 v18.8.1-pre
  ...


Reason sequential/test-debugger-clear-breakpoints
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44392/, https://github.com/nodejs/node/pull/44358/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46305/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Example
not ok 853 sequential/test-debugger-clear-breakpoints
  ---
  duration_ms: 10.841
  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: 
        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 v18.8.1-pre
  ...


Reason sequential/test-debugger-exec-scope
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44392/, https://github.com/nodejs/node/pull/44358/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46305/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Example
not ok 854 sequential/test-debugger-exec-scope
  ---
  duration_ms: 10.857
  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: 
        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 v18.8.1-pre
  ...


Reason sequential/test-debugger-object-type-remote-object
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44392/, https://github.com/nodejs/node/pull/44358/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46305/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Example
not ok 856 sequential/test-debugger-object-type-remote-object
  ---
  duration_ms: 120.816
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason sequential/test-debugger-profile
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44392/, https://github.com/nodejs/node/pull/44358/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46305/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Example
not ok 857 sequential/test-debugger-profile
  ---
  duration_ms: 10.925
  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: 
        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 v18.8.1-pre
  ...


Reason sequential/test-debugger-restart-message
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44392/, https://github.com/nodejs/node/pull/44358/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46305/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Example
not ok 858 sequential/test-debugger-restart-message
  ---
  duration_ms: 11.6
  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: 
        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 v18.8.1-pre
  ...


Reason sequential/test-debugger-use-strict
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44392/, https://github.com/nodejs/node/pull/44358/)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46305/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46350/
Example
not ok 859 sequential/test-debugger-use-strict
  ---
  duration_ms: 11.25
  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: 
        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 v18.8.1-pre
  ...


Reason sequential/test-diagnostic-dir-cpu-prof
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44450/, https://github.com/nodejs/node/pull/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. (10)
  • 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)
  • Failed to trigger sub builds (2)
  • error: remote GitHub already exists. (2)
  • sequential/test-heap-prof (7)
  • parallel/test-child-process-exec-timeout (6)
  • parallel/test-vm-timeout-escape-promise-2 (4)
  • parallel/test-zlib-unused-weak (4)
  • wpt/test-webcrypto (3)
  • addons/report-fatalerror/test (2)
  • parallel/test-heapsnapshot-near-heap-limit-worker (2)
  • parallel/test-http2-client-upload-reject (2)
  • parallel/test-inspector-esm (2)
  • sequential/test-child-process-execsync (2)
  • sequential/test-debugger-auto-resume (2)
  • sequential/test-debugger-clear-breakpoints (2)
  • sequential/test-debugger-exec-scope (2)
  • sequential/test-debugger-object-type-remote-object (2)
  • sequential/test-debugger-profile (2)
  • sequential/test-debugger-restart-message (2)
  • sequential/test-debugger-use-strict (2)
  • sequential/test-diagnostic-dir-cpu-prof (2)
Dominant language
Shell
Stars
57
Forks
20
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/reliability

All issues in nodejs/reliability

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.