nodejs / nodejs/reliability

CI Reliability 2022-09-04

Aperta
#367 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Lingua principale
Shell
Stelle
57
Fork
20
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Failures in node-test-pull-request/46305 to node-test-pull-request/46401 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-04 00:16 1 2 35 7 55 2.17%
Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 10 (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/, https://github.com/nodejs/node/pull/44327/)
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/46401/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 145.40.99.31/145.40.99.31:45024' 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: 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 ERROR: Build step failed with exception
Type BUILD_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/44279/, https://github.com/nodejs/node/pull/44358/, https://github.com/nodejs/node/pull/44500/)
Appeared test-equinix-ubuntu2004_container-armv7l-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46309/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46396/
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 workspace for ...
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/44475/, https://github.com/nodejs/node/pull/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

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 6 (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/46310/
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 5 (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/46308/
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 wpt/test-webcrypto
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/44467/, https://github.com/nodejs/node/pull/44468/, https://github.com/nodejs/node/pull/44486/, https://github.com/nodejs/node/pull/44500/, https://github.com/nodejs/node/pull/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 (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 parallel/test-vm-timeout-escape-promise-2
Type JS_TEST_FAILURE
Failed PR 3 (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
First CI https://ci.nodejs.org/job/node-test-pull-request/46314/
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 sequential/test-child-process-execsync
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/44392/, https://github.com/nodejs/node/pull/44358/, https://github.com/nodejs/node/pull/44500/)
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/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 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 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: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (4)
  • Failed to trigger node-test-commit (4)
  • ERROR: Build step failed with exception (3)
  • ERROR: Step ?Publish JUnit test result report? failed: no workspace for ... (2)
  • error: remote GitHub already exists. (2)
  • sequential/test-heap-prof (6)
  • parallel/test-child-process-exec-timeout (5)
  • wpt/test-webcrypto (5)
  • parallel/test-zlib-unused-weak (4)
  • parallel/test-vm-timeout-escape-promise-2 (3)
  • sequential/test-child-process-execsync (3)
  • addons/report-fatalerror/test (2)
  • parallel/test-heapsnapshot-near-heap-limit-worker (2)
  • parallel/test-http2-client-upload-reject (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)

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia esaminando gli esempi collegati della console Jenkins e i gruppi di errori ricorrenti: disconnessioni JNLP, fetch Git, errori di build/reporting e i due test JavaScript indicati. Confronta gli agent interessati e gli intervalli CI, quindi conferma che ogni categoria di errore viene risolta rieseguendo i job pertinenti e non blocca più più PR.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
git, node.js, shell
Ambito
ci-cd, devops, testing-qa
Tipo di issue
Bug
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
20/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.