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.

Sign up for GitHub

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

Jump to bottom

CI Reliability 2022-08-29 #361

Open
30 tasks
github-actions bot opened this issue Aug 29, 2022 · 0 comments
Open
30 tasks

CI Reliability 2022-08-29 #361

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

Comments

@github-actions
Copy link

Failures in node-test-pull-request/46203 to node-test-pull-request/46298 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-29 00:17 11 11 16 7 55 13.41%

JSTest Failure

Reason sequential/test-child-process-execsync
Type JS_TEST_FAILURE
Failed PR 10 (nodejs/node#44241, nodejs/node#44367, nodejs/node#43476, nodejs/node#44362, nodejs/node#44324, nodejs/node#44358, nodejs/node#44309, nodejs/node#44388, nodejs/node#44341, nodejs/node#44370)
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/46204/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46273/
Example 
not ok 851 sequential/test-child-process-execsync
  ---
  duration_ms: 5.51
  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 parallel/test-child-process-exec-timeout
Type JS_TEST_FAILURE
Failed PR 6 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44179, nodejs/node#44309, nodejs/node#44370, nodejs/node#44057)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46205/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46288/
Example 
not ok 106 parallel/test-child-process-exec-timeout
  ---
  duration_ms: 11.807
  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 parallel/test-vm-timeout-escape-promise-2
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44309, nodejs/node#44407, nodejs/node#44380, nodejs/node#44393, nodejs/node#44057)
Appeared test-azure_msft-win10_vs2019-x64-2, test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46219/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46298/
Example 
not ok 754 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 1.391
  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-debugger-backtrace
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301, nodejs/node#44355)
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/46208/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46266/
Example 
not ok 857 sequential/test-debugger-backtrace
  ---
  duration_ms: 9.722
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (5000) while waiting for /break (?:on start )?in/i; found: 
    < Debugger listening on ws://127.0.0.1:9229/b4aae9e5-e491-4b3b-b1d9-4ff3e9a24bdb
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    
    connecting to 127.0.0.1:9229 ...
     ok
    
    
    < Debugger attached.
    < 
    
        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 5 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301, nodejs/node#44355)
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/46208/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46266/
Example 
not ok 858 sequential/test-debugger-custom-port
  ---
  duration_ms: 10.146
  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 5 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301, nodejs/node#44355)
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/46208/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46266/
Example 
not ok 859 sequential/test-debugger-exec
  ---
  duration_ms: 9.635
  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 5 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301, nodejs/node#44355)
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/46208/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46266/
Example 
not ok 860 sequential/test-debugger-launch
  ---
  duration_ms: 10.204
  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 5 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301, nodejs/node#44355)
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/46208/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46266/
Example 
not ok 862 sequential/test-debugger-random-port-with-inspect-port
  ---
  duration_ms: 10.12
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (5000) while waiting for /break (?:on start )?in/i; found: 
    < Debugger listening on ws://127.0.0.1:63381/07389a8a-78e8-4cc4-9df4-18fd6b47f618
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    connecting to 127.0.0.1:63381 ...
     ok
    
    
    < Debugger attached.
    < 
    
        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 5 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44313, nodejs/node#44301, nodejs/node#44355)
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/46208/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46266/
Example 
not ok 864 sequential/test-debugger-watchers
  ---
  duration_ms: 9.956
  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 5 (nodejs/node#44241, nodejs/node#44313, nodejs/node#44380, nodejs/node#44309, nodejs/node#44057)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46204/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46298/
Example 
not ok 867 sequential/test-heap-prof
  ---
  duration_ms: 120.611
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...
Reason parallel/test-child-process-spawnsync-timeout
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44241, nodejs/node#44341, nodejs/node#44362, nodejs/node#44309)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46204/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46237/
Example 
not ok 120 parallel/test-child-process-spawnsync-timeout
  ---
  duration_ms: 6.562
  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 sequential/test-debugger-run-after-quit-restart
Type JS_TEST_FAILURE
Failed PR 4 (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/46208/
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 node-api/test_threadsafe_function/test
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44362, nodejs/node#44402, nodejs/node#44376)
Appeared test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46233/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46261/
Example 
not ok 3517 node-api/test_threadsafe_function/test
  ---
  duration_ms: 360.57
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...
Reason parallel/test-debugger-extract-function-name
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44241, nodejs/node#44393, nodejs/node#44327)
Appeared test-azure_msft-win10_vs2019-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-1, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46204/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46289/
Example 
not ok 201 parallel/test-debugger-extract-function-name
  ---
  duration_ms: 10.852
  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 3 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44358)
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/46204/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46241/
Example 
not ok 852 sequential/test-debugger-auto-resume
  ---
  duration_ms: 11.10
  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.7.1-pre
  ...
Reason sequential/test-debugger-break
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44313, nodejs/node#44301, nodejs/node#44327)
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/46220/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46289/
Example 
not ok 856 sequential/test-debugger-break
  ---
  duration_ms: 9.875
  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 3 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44358)
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/46204/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46241/
Example 
not ok 853 sequential/test-debugger-clear-breakpoints
  ---
  duration_ms: 11.23
  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.7.1-pre
  ...
Reason sequential/test-debugger-exec-scope
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44358)
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/46210/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46241/
Example 
not ok 854 sequential/test-debugger-exec-scope
  ---
  duration_ms: 10.831
  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.7.1-pre
  ...
Reason sequential/test-debugger-heap-profiler
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44313, nodejs/node#44301, nodejs/node#44327)
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/46220/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46289/
Example 
not ok 858 sequential/test-debugger-heap-profiler
  ---
  duration_ms: 9.712
  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: 
    < Debugger listening on ws://127.0.0.1:9229/8f2e6c97-ca7a-4705-b3a2-7c8f19b58dec
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    
    
    connecting to 127.0.0.1:9229 ...
        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 3 (nodejs/node#44313, nodejs/node#44301, nodejs/node#44327)
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/46220/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46289/
Example 
not ok 859 sequential/test-debugger-list
  ---
  duration_ms: 120.564
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...
Reason sequential/test-debugger-object-type-remote-object
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44358)
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/46210/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46241/
Example 
not ok 856 sequential/test-debugger-object-type-remote-object
  ---
  duration_ms: 120.778
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...
Reason sequential/test-debugger-preserve-breaks
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44313, nodejs/node#44301, nodejs/node#44327)
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/46220/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46289/
Example 
not ok 860 sequential/test-debugger-preserve-breaks
  ---
  duration_ms: 9.856
  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
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#43476, nodejs/node#44241, nodejs/node#44358)
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/46209/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46241/
Example 
not ok 857 sequential/test-debugger-profile
  ---
  duration_ms: 10.913
  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.7.1-pre
  ...
Reason sequential/test-debugger-restart-message
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44358)
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/46210/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46241/
Example 
not ok 858 sequential/test-debugger-restart-message
  ---
  duration_ms: 11.104
  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.7.1-pre
  ...
Reason sequential/test-debugger-use-strict
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44241, nodejs/node#43476, nodejs/node#44358)
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/46210/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46241/
Example 
not ok 859 sequential/test-debugger-use-strict
  ---
  duration_ms: 10.979
  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.7.1-pre
  ...
Reason report/test-report-fatalerror-oomerror
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44367, nodejs/node#44309)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46217/
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-random-port
Type JS_TEST_FAILURE
Failed PR 2 (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/46220/
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-sb-before-load
Type JS_TEST_FAILURE
Failed PR 2 (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/46220/
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-worker-prof
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44341, nodejs/node#44327)
Appeared test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/46223/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46289/
Example 
not ok 887 sequential/test-worker-prof
  ---
  duration_ms: 30.249
  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...

Jenkins Failure

Build Failure

Reason ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 6 (nodejs/node#43476, nodejs/node#44407, nodejs/node#44380, nodejs/node#44355, nodejs/node#44393, nodejs/node#44341)
Appeared test-azure_msft-win10_vs2019-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46251/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46269/
Example 
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Join notifier cannot find upstream run: node-test-binary-windows-js-suites number 16484
Finished: FAILURE

Progress

  • sequential/test-child-process-execsync (10)
  • parallel/test-child-process-exec-timeout (6)
  • parallel/test-vm-timeout-escape-promise-2 (5)
  • sequential/test-debugger-backtrace (5)
  • sequential/test-debugger-custom-port (5)
  • sequential/test-debugger-exec (5)
  • sequential/test-debugger-launch (5)
  • sequential/test-debugger-random-port-with-inspect-port (5)
  • sequential/test-debugger-watchers (5)
  • sequential/test-heap-prof (5)
  • parallel/test-child-process-spawnsync-timeout (4)
  • sequential/test-debugger-run-after-quit-restart (4)
  • node-api/test_threadsafe_function/test (3)
  • parallel/test-debugger-extract-function-name (3)
  • sequential/test-debugger-auto-resume (3)
  • sequential/test-debugger-break (3)
  • sequential/test-debugger-clear-breakpoints (3)
  • sequential/test-debugger-exec-scope (3)
  • sequential/test-debugger-heap-profiler (3)
  • sequential/test-debugger-list (3)
  • sequential/test-debugger-object-type-remote-object (3)
  • sequential/test-debugger-preserve-breaks (3)
  • sequential/test-debugger-profile (3)
  • sequential/test-debugger-restart-message (3)
  • sequential/test-debugger-use-strict (3)
  • report/test-report-fatalerror-oomerror (2)
  • sequential/test-debugger-random-port (2)
  • sequential/test-debugger-sb-before-load (2)
  • sequential/test-worker-prof (2)
  • ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (6)
@joyeecheung joyeecheung mentioned this issue Aug 29, 2022
Closed
joyeecheung added a commit to nodejs/node that referenced this issue Aug 31, 2022
@joyeecheung
test: make the vm timeout escape tests more lenient
2d22820 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: #44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
@joyeecheung
test: make the vm timeout escape tests more lenient
12f7635 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: nodejs#44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
@joyeecheung
test: make the vm timeout escape tests more lenient
abc3f87 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: nodejs#44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 5, 2022
@joyeecheung @RafaelGSS
test: make the vm timeout escape tests more lenient
aeaea85 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: #44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 6, 2022
@joyeecheung
test: make the vm timeout escape tests more lenient
5dd57ef 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: nodejs#44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 6, 2022
@joyeecheung @RafaelGSS
test: make the vm timeout escape tests more lenient
e884628 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: #44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 7, 2022
@joyeecheung @RafaelGSS
test: make the vm timeout escape tests more lenient
0af15c7 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: #44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
Fyko pushed a commit to Fyko/node that referenced this issue Sep 15, 2022
@joyeecheung @Fyko
test: make the vm timeout escape tests more lenient
15cdf39 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: nodejs#44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
targos pushed a commit to nodejs/node that referenced this issue Sep 16, 2022
@joyeecheung @targos
test: make the vm timeout escape tests more lenient
965a5b8 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: #44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 10, 2022
@joyeecheung @juanarbol
test: make the vm timeout escape tests more lenient
3a36bda 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: #44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 11, 2022
@joyeecheung @juanarbol
test: make the vm timeout escape tests more lenient
c3429ab 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: #44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
@joyeecheung @guangwong
test: make the vm timeout escape tests more lenient
1196343 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: nodejs/node#44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
@joyeecheung @guangwong
test: make the vm timeout escape tests more lenient
2802d1f 
Previously the tests required that Node.js finish the initialization
of the watchdog thread and fires the timeout within 100ms, which
can be difficult on certain systems under load. This patch
relaxes the requirement to 2000ms. If there is a bug and the
timeout can actually be escaped, raising the timeout to 2000ms
would not make a difference anyway.

PR-URL: nodejs/node#44433
Refs: nodejs/reliability#333
Refs: nodejs/reliability#361
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants