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-22 #354

Open
36 tasks
github-actions bot opened this issue Aug 22, 2022 · 0 comments
Open
36 tasks

CI Reliability 2022-08-22 #354

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

Comments

@github-actions
Copy link

Failures in node-test-pull-request/46038 to node-test-pull-request/46131 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-22 00:16 3 9 26 1 61 9.38%

JSTest Failure

Reason sequential/test-debugger-exceptions
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#44300, nodejs/node#44306, nodejs/node#44302, nodejs/node#44309, nodejs/node#44314)
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/46082/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46121/
Example 
not ok 857 sequential/test-debugger-exceptions
  ---
  duration_ms: 9.960
  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#44300, nodejs/node#44306, nodejs/node#44302, nodejs/node#44309, nodejs/node#44314)
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/46082/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46121/
Example 
not ok 858 sequential/test-debugger-help
  ---
  duration_ms: 9.802
  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#44300, nodejs/node#44306, nodejs/node#44302, nodejs/node#44309, nodejs/node#44314)
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/46082/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46121/
Example 
not ok 859 sequential/test-debugger-low-level
  ---
  duration_ms: 10.174
  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#44300, nodejs/node#44306, nodejs/node#44302, nodejs/node#44309, nodejs/node#44314)
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/46082/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46121/
Example 
not ok 860 sequential/test-debugger-profile-command
  ---
  duration_ms: 120.589
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...
Reason sequential/test-debugger-break
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44323, nodejs/node#44318, nodejs/node#44322, nodejs/node#44256)
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/46104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46126/
Example 
not ok 847 sequential/test-debugger-break
  ---
  duration_ms: 9.963
  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-breakpoint-exists
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44300, nodejs/node#44306, nodejs/node#44302, nodejs/node#44309)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46082/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46102/
Example 
not ok 855 sequential/test-debugger-breakpoint-exists
  ---
  duration_ms: 10.783
  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 4 (nodejs/node#44323, nodejs/node#44318, nodejs/node#44322, nodejs/node#44256)
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/46104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46126/
Example 
not ok 849 sequential/test-debugger-heap-profiler
  ---
  duration_ms: 10.73
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.848
    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/a1854067-44d3-496d-afda-9cee6bbe0b0e
    < 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 v18.7.1-pre
  ...
Reason sequential/test-debugger-list
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44323, nodejs/node#44318, nodejs/node#44322, nodejs/node#44256)
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/46104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46126/
Example 
not ok 850 sequential/test-debugger-list
  ---
  duration_ms: 120.562
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...
Reason sequential/test-debugger-random-port
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44323, nodejs/node#44318, nodejs/node#44322, nodejs/node#44256)
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/46104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46126/
Example 
not ok 852 sequential/test-debugger-random-port
  ---
  duration_ms: 9.701
  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:50399/749f6e1d-5022-4bcb-adc1-92961cfdef44
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    connecting to 127.0.0.1:50399 ...
     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 v18.7.1-pre
  ...
Reason sequential/test-debugger-sb-before-load
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44323, nodejs/node#44318, nodejs/node#44322, nodejs/node#44256)
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/46104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46126/
Example 
not ok 853 sequential/test-debugger-sb-before-load
  ---
  duration_ms: 10.159
  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/796cb1fc-da91-4b7d-9f31-dca9d7d1a22f
    < 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 v18.7.1-pre
  ...
Reason sequential/test-debugger-scripts
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44306, nodejs/node#44302, nodejs/node#44309, nodejs/node#44314)
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/46088/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46121/
Example 
not ok 862 sequential/test-debugger-scripts
  ---
  duration_ms: 10.172
  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#44269, nodejs/node#44309, nodejs/node#44304)
Appeared test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46062/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46113/
Example 
not ok 105 node-api/test_threadsafe_function/test
  ---
  duration_ms: 360.94
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...
Reason parallel/test-vm-timeout-escape-promise-2
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44203, nodejs/node#44284, nodejs/node#44302)
Appeared test-azure_msft-win10_vs2019-x64-4, test-rackspace-win2012r2_vs2013-x64-1, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46055/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46096/
Example 
not ok 752 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 0.356
  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-custom-port
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44318, nodejs/node#44314, nodejs/node#44322)
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/46111/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
not ok 857 sequential/test-debugger-custom-port
  ---
  duration_ms: 10.937
  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 3 (nodejs/node#44314, nodejs/node#44318, nodejs/node#44322)
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/46110/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
not ok 859 sequential/test-debugger-launch
  ---
  duration_ms: 11.77
  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-preserve-breaks
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44323, nodejs/node#44318, nodejs/node#44322)
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/46104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46120/
Example 
not ok 860 sequential/test-debugger-preserve-breaks
  ---
  duration_ms: 9.673
  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 3 (nodejs/node#44318, nodejs/node#44314, nodejs/node#44322)
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/46111/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
not ok 861 sequential/test-debugger-random-port-with-inspect-port
  ---
  duration_ms: 10.827
  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 3 (nodejs/node#44314, nodejs/node#44318, nodejs/node#44322)
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/46110/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
not ok 862 sequential/test-debugger-run-after-quit-restart
  ---
  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 v19.0.0-pre
  ...
Reason sequential/test-debugger-watchers
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44314, nodejs/node#44318, nodejs/node#44322)
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/46110/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
not ok 863 sequential/test-debugger-watchers
  ---
  duration_ms: 11.6
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (5000) while waiting for /break (?:on start )?in/i; found: 
        at Timeout.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84:18)
        at listOnTimeout (node:internal/timers:564:17)
        at process.processTimers (node:internal/timers:507:7)
    
    Node.js v19.0.0-pre
  ...
Reason sequential/test-heap-prof
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44314, nodejs/node#44318, nodejs/node#44322)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46110/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
not ok 866 sequential/test-heap-prof
  ---
  duration_ms: 120.820
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...
Reason sequential/test-http-regr-gh-2928
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44180, nodejs/node#44234, nodejs/node#44304)
Appeared test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46040/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46113/
Example 
not ok 3657 sequential/test-http-regr-gh-2928
  ---
  duration_ms: 120.121
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.
  ...
Reason parallel/test-child-process-exec-timeout
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44306, nodejs/node#44322)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46088/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
not ok 106 parallel/test-child-process-exec-timeout
  ---
  duration_ms: 12.223
  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-fs-write-stream-file-handle
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44302, nodejs/node#44314)
Appeared test-nearform-macos11.0-arm64-1, test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46093/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46121/
Example 
not ok 871 parallel/test-fs-write-stream-file-handle
  ---
  duration_ms: 0.60
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:124
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    + actual - expected
    
    + ''
    - 'hello world'
        at WriteStream.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx-arm/nodes/osx11/test/parallel/test-fs-write-stream-file-handle.js:19:12)
        at WriteStream.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx-arm/nodes/osx11/test/common/index.js:444:15)
        at WriteStream.emit (node:events:513:28)
        at emitCloseNT (node:internal/streams/destroy:132:10)
        at process.processTicksAndRejections (node:internal/process/task_queues:81:21) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '',
      expected: 'hello world',
      operator: 'strictEqual'
    }
    
    Node.js v19.0.0-pre
  ...
Reason parallel/test-inspector-multisession-ws
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44294, nodejs/node#44322)
Appeared test-nearform-macos10.15-x64-1, test-ibm-rhel8-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/46085/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46103/
Example 
not ok 1625 parallel/test-inspector-multisession-ws
  ---
  duration_ms: 15.504
  severity: fail
  exitcode: 1
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:64664/51f48724-a4a7-47c1-93eb-2f331d0fcec4
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] Debugger attached.
    [err] 
    [test] Breaking in code and verifying events are fired
    Timed out waiting for matching notification (Initial pause)
    1
  ...
Reason pummel/test-timers
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44252, nodejs/node#44323)
Appeared test-joyent-ubuntu1804-x64-1, test-orka-macos11-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46071/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46104/
Example 
not ok 3485 pummel/test-timers
  ---
  duration_ms: 2.64
  severity: fail
  exitcode: 1
  stack: |-
    diff: 1067
    diff: 1604
    node:assert:400
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
    
      assert.ok(t <= diff && diff < t + (WINDOW * interval_count))
    
        at Timeout.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux/test/pummel/test-timers.js:64:12)
        at Timeout._onTimeout (/home/iojs/build/workspace/node-test-commit-linux/test/common/index.js:444:15)
        at listOnTimeout (node:internal/timers:564:17)
        at process.processTimers (node:internal/timers:507:7) {
      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 2 (nodejs/node#44318, nodejs/node#44322)
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/46111/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
not ok 856 sequential/test-debugger-backtrace
  ---
  duration_ms: 10.988
  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 2 (nodejs/node#44318, nodejs/node#44322)
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/46111/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
not ok 858 sequential/test-debugger-exec
  ---
  duration_ms: 11.83
  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-diagnostic-dir-cpu-prof
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44304, nodejs/node#44323)
Appeared test-ibm-rhel7-s390x-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46086/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46104/
Example 
not ok 2942 sequential/test-diagnostic-dir-cpu-prof
  ---
  duration_ms: 0.196
  severity: fail
  exitcode: 1
  stack: |-
    Dispatching message { "id": 1, "method": "Profiler.enable" }
    Receive CPU profile message
    {"id":1,"result":{}}
    Dispatching message { "id": 2, "method": "Profiler.start" }
    Receive CPU profile message
    {"id":2,"result":{}}
    Dispatching message { "id": 3, "method": "Profiler.setSamplingInterval", "params": { "interval": 50 } }
    Receive CPU profile message
    {"error":{"code":-32000,"message":"Cannot change sampling interval when profiling."},"id":3}
    EndStartedProfilers
    V8CpuProfilerConnection::End(), ending = false
    Dispatching message { "id": 4, "method": "Profiler.stop" }
    Receive CPU profile message
    Writing profile response (id = 4)
    Written result to /home/iojs/node-tmp/.tmp.0/prof/CPU.20220820.061055.62504.0.001.cpuprofile
    
    [
      {
        id: 1,
        callFrame: {
          functionName: '(root)',
          scriptId: '0',
   ...
Reason sequential/test-perf-hooks
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44284, nodejs/node#44304)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46068/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46086/
Example 
not ok 3601 sequential/test-perf-hooks
  ---
  duration_ms: 2.14
  severity: fail
  exitcode: 1
  stack: |-
    {
      name: 'node',
      entryType: 'node',
      startTime: 0,
      duration: { around: 23.780235290527344 },
      nodeStart: { around: 0 },
      v8Start: { around: 0 },
      bootstrapComplete: { around: 23.759666442871094, delay: 2500 },
      environment: { around: 0 },
      loopStart: -1,
      loopExit: -1
    }
    {
      name: 'node',
      entryType: 'node',
      startTime: 0,
      duration: { around: 1028.3518257141113 },
      nodeStart: { around: 0 },
      v8Start: { around: 0 },
      bootstrapComplete: { around: 23.759666442871094, delay: 2500 },
      environment: { around: 0 },
      loopStart: { around: 23.759666442871094, delay: 2500 },
      loopExit: -1
    }
    {
      name: 'node',
      entryType: 'node',
      startTime: 0,
      duration: { around: 1029.3665046691895 },
      nodeStart: { around: 0 },
      v8Start: { around: 0 },
      bootstrapComplete: { aroun...

Jenkins Failure

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 4 (nodejs/node#44234, nodejs/node#44248, nodejs/node#44299, nodejs/node#44322)
Appeared test-digitalocean-freebsd12-x64-2, test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46039/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46103/
Example 
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:55801' 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#43253, nodejs/node#44252)
Appeared test-softlayer-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46046/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46072/
Example 
Build timed out (after 60 minutes). Marking the build as failed.

Git 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 2 (nodejs/node#44156, nodejs/node#44322)
Appeared test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian10_container-armv7l-2, test-equinix-debian10_container-armv7l-1, test-joyent-smartos20-x64-3, test-osuosl-aix72-ppc64_be-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46038/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
[PostBuildScript] - [INFO] Executing post build scripts.
[node-test-binary-armv7l] $ /bin/bash -ex /tmp/jenkins5392350968826366432.sh
+ '[' -d .git ']'
+ git clean -fdx
Reason ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#44252, nodejs/node#44294)
Appeared test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46071/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46078/
Example 
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-freebsd/nodes=freebsd12-x64 #45486
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
Reason ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#44322, nodejs/node#44304)
Appeared test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vs2019-x64-1, test-rackspace-win2012r2_vs2017-x64-3, test-rackspace-win2012r2_vs2017-x64-1, test-rackspace-win2012r2_vs2013-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46103/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46113/
Example 
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
Reason Error: [WinError 5] Access is denied: 'C:\Users\Administrator\clcache\stats.txt.new' -> 'C:\Users\Administrator\clcache\stats.txt'
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#44203, nodejs/node#44307)
Appeared test-rackspace-win2012r2_vs2019-x64-2, test-rackspace-win2012r2_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/46053/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46091/
Example 
Error: [WinError 5] Access is denied: 'C:\\Users\\Administrator\\clcache\\stats.txt.new' -> 'C:\\Users\\Administrator\\clcache\\stats.txt'
  [8164] Failed to execute script clcache_main
  units_data.cpp
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(523,5): error MSB6006: "clcache_main.exe" exited with code -1. [C:\workspace\node-compile-windows-debug\node\tools\icu\icutools.vcxproj]
  unumsys.cpp
  uregex.cpp

undefined

Reason Unknown
Type undefined
Failed PR 16 (nodejs/node#44203, nodejs/node#44269, nodejs/node#44284, nodejs/node#44293, nodejs/node#44300, nodejs/node#44306, nodejs/node#44307, nodejs/node#44255, nodejs/node#44302, nodejs/node#44309, nodejs/node#44323, nodejs/node#44318, nodejs/node#44304, nodejs/node#44256, nodejs/node#44314, nodejs/node#44322)
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/46055/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46131/
Example 
Unknown

Progress

  • 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-break (4)
  • sequential/test-debugger-breakpoint-exists (4)
  • sequential/test-debugger-heap-profiler (4)
  • sequential/test-debugger-list (4)
  • sequential/test-debugger-random-port (4)
  • sequential/test-debugger-sb-before-load (4)
  • sequential/test-debugger-scripts (4)
  • node-api/test_threadsafe_function/test (3)
  • parallel/test-vm-timeout-escape-promise-2 (3)
  • sequential/test-debugger-custom-port (3)
  • sequential/test-debugger-launch (3)
  • sequential/test-debugger-preserve-breaks (3)
  • sequential/test-debugger-random-port-with-inspect-port (3)
  • sequential/test-debugger-run-after-quit-restart (3)
  • sequential/test-debugger-watchers (3)
  • sequential/test-heap-prof (3)
  • sequential/test-http-regr-gh-2928 (3)
  • parallel/test-child-process-exec-timeout (2)
  • parallel/test-fs-write-stream-file-handle (2)
  • parallel/test-inspector-multisession-ws (2)
  • pummel/test-timers (2)
  • sequential/test-debugger-backtrace (2)
  • sequential/test-debugger-exec (2)
  • sequential/test-diagnostic-dir-cpu-prof (2)
  • sequential/test-perf-hooks (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (4)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
  • ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (2)
  • Error: [WinError 5] Access is denied: 'C:\\Users\\Administrator\\clcache\\stats.txt.new' -> 'C:\\Users\\Administrator\\clcache\\stats.txt' (2)
  • Unknown (16)
This was referenced Aug 22, 2022
Closed
Closed
Closed
joyeecheung added a commit to nodejs/node that referenced this issue Sep 1, 2022
@joyeecheung
test: avoid race in file write stream handle tests
4e6fdb3 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: #44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
@joyeecheung
test: avoid race in file write stream handle tests
ad68f7f 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: nodejs#44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 1, 2022
@joyeecheung
test: avoid race in file write stream handle tests
4189825 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: nodejs#44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 5, 2022
@joyeecheung @RafaelGSS
test: avoid race in file write stream handle tests
f803d38 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: #44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
joyeecheung added a commit to joyeecheung/node that referenced this issue Sep 6, 2022
@joyeecheung
test: avoid race in file write stream handle tests
5aad691 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: nodejs#44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 6, 2022
@joyeecheung @RafaelGSS
test: avoid race in file write stream handle tests
46bb126 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: #44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 7, 2022
@joyeecheung @RafaelGSS
test: avoid race in file write stream handle tests
4c33e5d 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: #44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
Fyko pushed a commit to Fyko/node that referenced this issue Sep 15, 2022
@joyeecheung @Fyko
test: avoid race in file write stream handle tests
789dc26 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: nodejs#44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
targos pushed a commit to nodejs/node that referenced this issue Sep 16, 2022
@joyeecheung @targos
test: avoid race in file write stream handle tests
1d8c955 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: #44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 10, 2022
@joyeecheung @juanarbol
test: avoid race in file write stream handle tests
e02d26f 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: #44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 11, 2022
@joyeecheung @juanarbol
test: avoid race in file write stream handle tests
5af3a5d 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: #44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
@joyeecheung @guangwong
test: avoid race in file write stream handle tests
8d9bbe4 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: nodejs/node#44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
@joyeecheung @guangwong
test: avoid race in file write stream handle tests
885468a 
The test previously created two fs.promises.open calls on the
same file with w+ back-to-back, and one of them could fail
when checking the contents of that file if the other happened
to be opening the file for write. Split them into different
tests (with different tmpdir) to avoid the race.

PR-URL: nodejs/node#44380
Refs: nodejs/reliability#354
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
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