Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI Reliability 2022-08-24 #356

Open
32 of 38 tasks
github-actions bot opened this issue Aug 24, 2022 · 0 comments
Open
32 of 38 tasks

CI Reliability 2022-08-24 #356

github-actions bot opened this issue Aug 24, 2022 · 0 comments

Comments

@github-actions
Copy link

github-actions bot commented Aug 24, 2022

Failures in node-test-pull-request/46139 to node-test-pull-request/46230 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-24 18:31 9 9 8 5 69 10.47%

Jenkins Failure

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 3 (nodejs/node#44353, nodejs/node#44358, nodejs/node#43476)
Appeared test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vs2019-x64-4, test-digitalocean-freebsd12-x64-1, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46170/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46209/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 20.213.108.146/20.213.108.146:3009' 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#44327, nodejs/node#43476)
Appeared test-rackspace-win2012r2_vs2019-x64-6, test-softlayer-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46177/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46196/
Example
Build timed out (after 60 minutes). Marking the build as failed.

Build Failure

undefined

Reason Unknown
Type undefined
Failed PR 23 (nodejs/node#44314, nodejs/node#44283, nodejs/node#44342, nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44255, nodejs/node#44359, nodejs/node#44349, nodejs/node#44247, nodejs/node#44358, nodejs/node#44353, nodejs/node#44250, nodejs/node#44345, nodejs/node#44319, nodejs/node#43476, nodejs/node#44241, nodejs/node#44313, nodejs/node#44074, nodejs/node#44301, nodejs/node#44309, nodejs/node#44367)
Appeared test-nearform_arm-win10_vs2019-arm64-1, test-equinix-debian10_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46142/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46230/
Example
Unknown

JSTest Failure

Reason sequential/test-child-process-execsync
Type JS_TEST_FAILURE
Failed PR 15 (nodejs/node#44314, nodejs/node#44283, nodejs/node#44342, nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44255, nodejs/node#44353, nodejs/node#44358, nodejs/node#44250, nodejs/node#44345, nodejs/node#44241, nodejs/node#44309, nodejs/node#44367)
Appeared test-azure_msft-win10_vs2019-x64-2, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46142/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46230/
Example
not ok 851 sequential/test-child-process-execsync
  ---
  duration_ms: 5.220
  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:86:12)
        at node:internal/main/run_main_module:23:47 {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v19.0.0-pre
  ...


Reason sequential/test-debugger-backtrace
Type JS_TEST_FAILURE
Failed PR 11 (nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44359, nodejs/node#44345, nodejs/node#44319, nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46159/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46224/
Example
not ok 856 sequential/test-debugger-backtrace
  ---
  duration_ms: 10.971
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-custom-port
Type JS_TEST_FAILURE
Failed PR 11 (nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44359, nodejs/node#44345, nodejs/node#44319, nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46159/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46224/
Example
not ok 857 sequential/test-debugger-custom-port
  ---
  duration_ms: 10.785
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-exec
Type JS_TEST_FAILURE
Failed PR 11 (nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44359, nodejs/node#44345, nodejs/node#44319, nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46159/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46224/
Example
not ok 858 sequential/test-debugger-exec
  ---
  duration_ms: 10.923
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-sb-before-load
Type JS_TEST_FAILURE
Failed PR 11 (nodejs/node#44342, nodejs/node#44252, nodejs/node#44309, nodejs/node#44327, nodejs/node#44255, nodejs/node#44349, nodejs/node#44247, nodejs/node#44358, nodejs/node#44319, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46146/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46226/
Example
not ok 862 sequential/test-debugger-sb-before-load
  ---
  duration_ms: 10.957
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-auto-resume
Type JS_TEST_FAILURE
Failed PR 10 (nodejs/node#44322, nodejs/node#44314, nodejs/node#44252, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44250, nodejs/node#44345, nodejs/node#44241, nodejs/node#43476)
Appeared 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/46139/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46209/
Example
not ok 856 sequential/test-debugger-auto-resume
  ---
  duration_ms: 10.838
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-exec-scope
Type JS_TEST_FAILURE
Failed PR 10 (nodejs/node#44322, nodejs/node#44314, nodejs/node#44252, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44250, nodejs/node#44345, nodejs/node#43476, nodejs/node#44241)
Appeared 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/46139/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46210/
Example
not ok 859 sequential/test-debugger-exec-scope
  ---
  duration_ms: 11.11
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-launch
Type JS_TEST_FAILURE
Failed PR 10 (nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44359, nodejs/node#44345, nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46159/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46224/
Example
not ok 859 sequential/test-debugger-launch
  ---
  duration_ms: 10.970
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-list
Type JS_TEST_FAILURE
Failed PR 10 (nodejs/node#44342, nodejs/node#44252, nodejs/node#44309, nodejs/node#44327, nodejs/node#44255, nodejs/node#44247, nodejs/node#44358, nodejs/node#44319, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46146/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46226/
Example
not ok 859 sequential/test-debugger-list
  ---
  duration_ms: 120.819
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason sequential/test-debugger-preserve-breaks
Type JS_TEST_FAILURE
Failed PR 10 (nodejs/node#44342, nodejs/node#44327, nodejs/node#44252, nodejs/node#44309, nodejs/node#44255, nodejs/node#44358, nodejs/node#44247, nodejs/node#44319, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46146/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46226/
Example
not ok 860 sequential/test-debugger-preserve-breaks
  ---
  duration_ms: 10.892
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-random-port-with-inspect-port
Type JS_TEST_FAILURE
Failed PR 10 (nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44359, nodejs/node#44345, nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46159/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46224/
Example
not ok 861 sequential/test-debugger-random-port-with-inspect-port
  ---
  duration_ms: 10.861
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-run-after-quit-restart
Type JS_TEST_FAILURE
Failed PR 10 (nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44359, nodejs/node#44345, nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46159/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46224/
Example
not ok 862 sequential/test-debugger-run-after-quit-restart
  ---
  duration_ms: 10.928
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-watchers
Type JS_TEST_FAILURE
Failed PR 10 (nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44359, nodejs/node#44345, nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46159/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46224/
Example
not ok 863 sequential/test-debugger-watchers
  ---
  duration_ms: 10.854
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-break
Type JS_TEST_FAILURE
Failed PR 9 (nodejs/node#44342, nodejs/node#44327, nodejs/node#44252, nodejs/node#44255, nodejs/node#44247, nodejs/node#44358, nodejs/node#44319, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46146/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46226/
Example
not ok 856 sequential/test-debugger-break
  ---
  duration_ms: 10.917
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-clear-breakpoints
Type JS_TEST_FAILURE
Failed PR 9 (nodejs/node#44322, nodejs/node#44314, nodejs/node#44252, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44345, nodejs/node#44241, nodejs/node#43476)
Appeared 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/46139/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46209/
Example
not ok 857 sequential/test-debugger-clear-breakpoints
  ---
  duration_ms: 11.37
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-heap-profiler
Type JS_TEST_FAILURE
Failed PR 9 (nodejs/node#44342, nodejs/node#44327, nodejs/node#44252, nodejs/node#44255, nodejs/node#44247, nodejs/node#44358, nodejs/node#44319, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46146/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46226/
Example
not ok 858 sequential/test-debugger-heap-profiler
  ---
  duration_ms: 11.16
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.857
    Files blocking: []
    
    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 v19.0.0-pre
  ...


Reason sequential/test-debugger-object-type-remote-object
Type JS_TEST_FAILURE
Failed PR 9 (nodejs/node#44322, nodejs/node#44314, nodejs/node#44252, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44345, nodejs/node#43476, nodejs/node#44241)
Appeared 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/46139/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46210/
Example
not ok 861 sequential/test-debugger-object-type-remote-object
  ---
  duration_ms: 120.510
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason sequential/test-debugger-restart-message
Type JS_TEST_FAILURE
Failed PR 9 (nodejs/node#44322, nodejs/node#44252, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44250, nodejs/node#44345, nodejs/node#43476, nodejs/node#44241)
Appeared 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/46139/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46210/
Example
not ok 863 sequential/test-debugger-restart-message
  ---
  duration_ms: 10.935
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-random-port
Type JS_TEST_FAILURE
Failed PR 8 (nodejs/node#44342, nodejs/node#44252, nodejs/node#44309, nodejs/node#44255, nodejs/node#44247, nodejs/node#44319, nodejs/node#44313, nodejs/node#44301)
Appeared 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/46146/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46226/
Example
not ok 861 sequential/test-debugger-random-port
  ---
  duration_ms: 11.133
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-use-strict
Type JS_TEST_FAILURE
Failed PR 8 (nodejs/node#44252, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44250, nodejs/node#44345, nodejs/node#43476, nodejs/node#44241)
Appeared 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/46160/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46210/
Example
not ok 864 sequential/test-debugger-use-strict
  ---
  duration_ms: 10.898
  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 v19.0.0-pre
  ...


Reason sequential/test-heap-prof
Type JS_TEST_FAILURE
Failed PR 8 (nodejs/node#44301, nodejs/node#44322, nodejs/node#44252, nodejs/node#44355, nodejs/node#44327, nodejs/node#44241, nodejs/node#44309, nodejs/node#44313)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46141/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46220/
Example
not ok 866 sequential/test-heap-prof
  ---
  duration_ms: 120.806
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason parallel/test-child-process-exec-timeout
Type JS_TEST_FAILURE
Failed PR 7 (nodejs/node#44314, nodejs/node#44252, nodejs/node#44309, nodejs/node#44327, nodejs/node#44345, nodejs/node#44241, nodejs/node#43476)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46142/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46209/
Example
not ok 106 parallel/test-child-process-exec-timeout
  ---
  duration_ms: 11.822
  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 Socket.<anonymous> (node:internal/child_process:449:11)
        at Socket.emit (node:events:513:28)
        at Pipe.<anonymous> (node:net:298:12)
    
    Node.js v19.0.0-pre
  ...


Reason sequential/test-debugger-profile
Type JS_TEST_FAILURE
Failed PR 7 (nodejs/node#44322, nodejs/node#44252, nodejs/node#44353, nodejs/node#44358, nodejs/node#44345, nodejs/node#43476, nodejs/node#44241)
Appeared 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/46139/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46210/
Example
not ok 862 sequential/test-debugger-profile
  ---
  duration_ms: 11.59
  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 v19.0.0-pre
  ...


Reason parallel/test-debugger-extract-function-name
Type JS_TEST_FAILURE
Failed PR 6 (nodejs/node#44283, nodejs/node#44309, nodejs/node#44349, nodejs/node#44301, nodejs/node#44319, nodejs/node#44241)
Appeared 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/46144/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46204/
Example
not ok 204 parallel/test-debugger-extract-function-name
  ---
  duration_ms: 16.632
  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 v19.0.0-pre
  ...


Reason report/test-report-fatalerror-oomerror
Type JS_TEST_FAILURE
Failed PR 6 (nodejs/node#44322, nodejs/node#44341, nodejs/node#44324, nodejs/node#44353, nodejs/node#44367, nodejs/node#44309)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46145/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46229/
Example
not ok 867 report/test-report-fatalerror-oomerror
  ---
  duration_ms: 300.88
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason sequential/test-debugger-breakpoint-exists
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44283, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44241)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46144/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46213/
Example
not ok 856 sequential/test-debugger-breakpoint-exists
  ---
  duration_ms: 11.82
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-exceptions
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44283, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44241)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46144/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46213/
Example
not ok 857 sequential/test-debugger-exceptions
  ---
  duration_ms: 10.911
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-help
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44283, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44241)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46144/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46213/
Example
not ok 858 sequential/test-debugger-help
  ---
  duration_ms: 11.191
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-low-level
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44283, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44241)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46144/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46213/
Example
not ok 859 sequential/test-debugger-low-level
  ---
  duration_ms: 11.62
  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 v19.0.0-pre
  ...


Reason sequential/test-debugger-profile-command
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44283, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44241)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46144/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46213/
Example
not ok 860 sequential/test-debugger-profile-command
  ---
  duration_ms: 120.877
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason sequential/test-debugger-scripts
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44283, nodejs/node#44309, nodejs/node#44353, nodejs/node#44358, nodejs/node#44241)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46144/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46213/
Example
not ok 862 sequential/test-debugger-scripts
  ---
  duration_ms: 10.915
  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 v19.0.0-pre
  ...


Reason parallel/test-child-process-spawnsync-timeout
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44283, nodejs/node#44319, nodejs/node#44241, nodejs/node#44309)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46144/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46219/
Example
not ok 120 parallel/test-child-process-spawnsync-timeout
  ---
  duration_ms: 7.221
  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\parallel\test-child-process-spawnsync-timeout.js:47:5)
        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:86:12)
        at node:internal/main/run_main_module:23:47 {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v19.0.0-pre
...

Reason parallel/test-vm-timeout-escape-promise-2
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44327, nodejs/node#44309)
Appeared test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vs2019-x64-2, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46173/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46219/
Example
not ok 753 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 0.397
  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-worker-prof
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44322, nodejs/node#44345)
Appeared test-rackspace-win2012r2_vs2013-x64-1, test-rackspace-win2012r2_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46154/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46187/
Example
not ok 887 sequential/test-worker-prof
  ---
  duration_ms: 30.301
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:124
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child exited with signal: {
      error: Error: spawnSync C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe ETIMEDOUT
          at Object.spawnSync (node:internal/child_process:1110:20)
          at spawnSync (node:child_process:857:24)
          at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:53:23)
          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:86:12)
          at node:internal/main/run_main...

Reason wpt/test-webcrypto
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44309, nodejs/node#44353)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46165/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46170/
Example
not ok 888 wpt/test-webcrypto
  ---
  duration_ms: 720.933
  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 ----
    ...

Progress

  • Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • Unknown (23)
  • sequential/test-child-process-execsync (15) test: raise sleep times in child process tests node#44375
  • sequential/test-debugger-backtrace (11) debugger: various fixes to the debugger and the debugger tests node#44359 (also fixes other debugger tests)
  • sequential/test-debugger-custom-port (11)
  • sequential/test-debugger-exec (11)
  • sequential/test-debugger-sb-before-load (11)
  • sequential/test-debugger-auto-resume (10)
  • sequential/test-debugger-exec-scope (10)
  • sequential/test-debugger-launch (10)
  • sequential/test-debugger-list (10)
  • sequential/test-debugger-preserve-breaks (10)
  • sequential/test-debugger-random-port-with-inspect-port (10)
  • sequential/test-debugger-run-after-quit-restart (10)
  • sequential/test-debugger-watchers (10)
  • sequential/test-debugger-break (9)
  • sequential/test-debugger-clear-breakpoints (9)
  • sequential/test-debugger-heap-profiler (9)
  • sequential/test-debugger-object-type-remote-object (9)
  • sequential/test-debugger-restart-message (9)
  • sequential/test-debugger-random-port (8)
  • sequential/test-debugger-use-strict (8)
  • sequential/test-heap-prof (8) test: split heap prof tests node#44388
  • parallel/test-child-process-exec-timeout (7) test: deflake child process exec timeout tests node#44390
  • sequential/test-debugger-profile (7)
  • parallel/test-debugger-extract-function-name (6)
  • report/test-report-fatalerror-oomerror (6) test: split report OOM tests node#44389
  • sequential/test-debugger-breakpoint-exists (5)
  • sequential/test-debugger-exceptions (5)
  • sequential/test-debugger-help (5)
  • sequential/test-debugger-low-level (5)
  • sequential/test-debugger-profile-command (5)
  • sequential/test-debugger-scripts (5)
  • parallel/test-child-process-spawnsync-timeout (4): test: raise sleep times in child process tests node#44375
  • parallel/test-vm-timeout-escape-promise-2 (2)
  • sequential/test-worker-prof (2)
  • wpt/test-webcrypto (2)
legendecas pushed a commit to nodejs/node that referenced this issue Aug 29, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: #44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
joyeecheung added a commit to nodejs/node that referenced this issue Aug 31, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: #44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
joyeecheung added a commit to nodejs/node that referenced this issue Aug 31, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: #44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: nodejs#44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: nodejs#44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: nodejs#44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: nodejs#44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: nodejs#44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: nodejs#44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 5, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: #44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 5, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: #44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 5, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: #44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 6, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: nodejs#44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 6, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: nodejs#44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 6, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: #44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 6, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: #44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 7, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: #44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 7, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: #44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Fyko pushed a commit to Fyko/node that referenced this issue Sep 15, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: nodejs#44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Fyko pushed a commit to Fyko/node that referenced this issue Sep 15, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: nodejs#44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Fyko pushed a commit to Fyko/node that referenced this issue Sep 15, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: nodejs#44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
targos pushed a commit to nodejs/node that referenced this issue Sep 16, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: #44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
targos pushed a commit to nodejs/node that referenced this issue Sep 16, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: #44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 3, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: #44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 4, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: #44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 4, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: #44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 7, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: #44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 10, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: #44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 10, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: #44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 10, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: #44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 11, 2022
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: #44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 11, 2022
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: #44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 11, 2022
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: #44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: nodejs/node#44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: nodejs/node#44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: nodejs/node#44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
The original heap prof tests can take too long to complete on
azure Windows machines, resulting in timeouts. Split them into
smaller tests and move them into the parallel directory to
speed up the execution.

PR-URL: nodejs/node#44388
Refs: nodejs/reliability#356
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
On Windows it might take too long for the parent to start the
communication with a child process, so by the time the parent
starts its own timer, the child process might have already
completed running, and the parent in those tests won't have a
chance to terminate these child processes after the timeout.
To address this issue, raise the time for which the child is
supposed to run to make sure that the parent starts
its own timer before the child terminates in the tests.
Also, split the test into smaller ones to reduce the overhead.

PR-URL: nodejs/node#44390
Refs: nodejs/reliability#356
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
On some machines the report OOM tests can take too long to complete,
resulting in a timeout. This splits the test into several different
smaller tests to reduce the flakiness of it.

PR-URL: nodejs/node#44389
Refs: nodejs/reliability#356
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants