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 2023-09-27 #676

Open
21 tasks
github-actions bot opened this issue Sep 27, 2023 · 0 comments
Open
21 tasks

CI Reliability 2023-09-27 #676

github-actions bot opened this issue Sep 27, 2023 · 0 comments

Comments

@github-actions
Copy link

Failures in node-test-pull-request/54170 to node-test-pull-request/54263 that failed 2 or more 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
2023-09-27 00:12 9 15 13 8 55 18.07%

JSTest Failure

Reason parallel/test-inspector-scriptparsed-context
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49654, nodejs/node#49834, nodejs/node#49740)
Appeared test-ibm-rhel8-s390x-1, test-equinix-ubuntu2004_container-armv7l-1, test-ibm-rhel8-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/54179/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54223/
Example
not ok 1896 parallel/test-inspector-scriptparsed-context
  ---
  duration_ms: 15493.22000
  severity: fail
  exitcode: 1
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:34309/0100c01e-869f-49a5-8969-78aca9c6b45f
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] 
    Timed out waiting for matching notification (break on [eval]:2)
    1
  ...


Reason parallel/test-tls-socket-close
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49750, nodejs/node#49859, nodejs/node#49790)
Appeared test-ibm-rhel8-s390x-4, test-ibm-rhel8-s390x-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54199/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54232/
Example
not ok 2867 parallel/test-tls-socket-close
  ---
  duration_ms: 204.65800
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    false !== true
    
        at Immediate._onImmediate (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-tls-socket-close.js:49:18)
        at process.processImmediate (node:internal/timers:478:21) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: 'strictEqual'
    }
    
    Node.js v21.0.0-pre
  ...


Reason sequential/test-http-regr-gh-2928
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49752, nodejs/node#49756, nodejs/node#49846)
Appeared test-azure_msft-win2016_vs2017-x64-6, test-azure_msft-win2016_vs2017-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/54181/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54263/
Example
not ok 934 sequential/test-http-regr-gh-2928
  ---
  duration_ms: 545.48900
  severity: fail
  exitcode: 3221226505
  stack: |-
    .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.
  ...


Reason sequential/test-net-connect-econnrefused
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49654, nodejs/node#49834, nodejs/node#49750)
Appeared test-ibm-rhel7-s390x-3
First CI https://ci.nodejs.org/job/node-test-pull-request/54179/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54202/
Example
not ok 3711 sequential/test-net-connect-econnrefused
  ---
  duration_ms: 120.23
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    pending 50 rounds 1
    pending 49 rounds 1
    pending 48 rounds 1
    pending 47 rounds 1
    pending 46 rounds 1
    pending 45 rounds 1
    pending 44 rounds 1
    pending 43 rounds 1
    pending 42 rounds 1
    pending 41 rounds 1
    pending 40 rounds 1
    pending 39 rounds 1
    pending 38 rounds 1
    pending 37 rounds 1
    pending 36 rounds 1
    pending 35 rounds 1
    pending 34 rounds 1
    pending 33 rounds 1
    pending 32 rounds 1
    pending 31 rounds 1
    pending 30 rounds 1
    pending 29 rounds 1
    pending 28 rounds 1
    pending 27 rounds 1
    pending 26 rounds 1
    pending 25 rounds 1
    pending 24 rounds 1
    pending 23 rounds 1
    pending 22 rounds 1
    pending 21 rounds 1
    pending 20 rounds 1
    pending 19 rounds 1
    pending 18 rounds 1
    pending 17 rounds 1
    pending 16 rounds 1
    pending 15 rounds 1
    pending 14 rounds ...

Reason sequential/test-perf-hooks
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#49804, nodejs/node#49856, nodejs/node#49863)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-orka-macos11-x64-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/54212/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54252/
Example
not ok 3999 sequential/test-perf-hooks
  ---
  duration_ms: 161.06900
  severity: fail
  exitcode: 1
  stack: |-
    check initial nodeTiming
    {
      "name": "node",
      "entryType": "node",
      "startTime": 0,
      "duration": 93.88645935058594,
      "nodeStart": 0.7065563201904297,
      "v8Start": 13.36221694946289,
      "environment": 22.879623413085938,
      "loopStart": -1,
      "loopExit": -1,
      "bootstrapComplete": 39.54657173156738,
      "idleTime": 0
    }
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: now (112.08127975463867) - timing.duration (93.88645935058594) = 18.194820404052734 >= 10
        at checkNodeTiming (/home/iojs/build/workspace/node-test-commit-linux-containered/test/sequential/test-perf-hooks.js:104:3)
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/sequential/test-perf-hooks.js:119:1)
        at Module._compile (node:internal/modules/cjs/loader:1429:14)
        at Module....

Reason parallel/test-cluster-fork-stdio
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49772, nodejs/node#49756)
Appeared test-rackspace-win2012r2_vs2015-x64-1, test-azure_msft-win11_vs2022-arm64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/54196/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54240/
Example
not ok 908 parallel/test-cluster-fork-stdio
  ---
  duration_ms: 120115.95100
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason parallel/test-fs-rmdir-recursive
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49846, nodejs/node#49854)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-digitalocean-freebsd12-x64-2, test-orka-macos11-x64-1, test-digitalocean-alpine315_container-x64-2, test-digitalocean-alpine318_container-x64-1, test-rackspace-debian10-x64-1, test-digitalocean-fedora32-x64-1, test-digitalocean-fedora38-x64-2, test-ibm-rhel8-x64-1, test-equinix_mnx-ubuntu1804-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54205/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54208/
Example
not ok 1508 parallel/test-fs-rmdir-recursive
  ---
  duration_ms: 120015.87100
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    (node:28303) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
    (Use `node --trace-deprecation ...` to show where the warning was created)
  ...


Reason parallel/test-fs-write-stream-eagain
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49834, nodejs/node#49846)
Appeared test-ibm-aix72-ppc64_be-1, test-osuosl-rhel8-ppc64_le-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54191/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54229/
Example
not ok 1228 parallel/test-fs-write-stream-eagain
  ---
  duration_ms: 622.77000
  severity: fail
  exitcode: 1
  stack: |-
    TAP version 13
    # Subtest: WriteStream EAGAIN
        # Subtest: _write
        not ok 1 - _write
          ---
          duration_ms: 69.812623
          location: 'file:///home/iojs/build/workspace/node-test-commit-aix/nodes/aix72-ppc64/test/parallel/test-fs-write-stream-eagain.mjs:15:3'
          failureType: 'testCodeFailure'
          error: |-
            Expected values to be strictly equal:
            
            '' !== 'foo'
            
          code: 'ERR_ASSERTION'
          name: 'AssertionError'
          expected: 'foo'
          actual: ''
          operator: 'strictEqual'
          stack: |-
            TestContext.<anonymous> (file:///home/iojs/build/workspace/node-test-commit-aix/nodes/aix72-ppc64/test/parallel/test-fs-write-stream-eagain.mjs:30:12)
            process.processTicksAndRejections (node:internal/process/task_queues:95:5)
            async Test.ru...

Reason parallel/test-http-server-request-timeouts-mixed
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49834, nodejs/node#49862)
Appeared test-ibm-rhel8-s390x-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54185/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54222/
Example
not ok 1378 parallel/test-http-server-request-timeouts-mixed
  ---
  duration_ms: 3352.56900
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
    
      assert(request2.completed)
    
        at Timeout._onTimeout (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-http-server-request-timeouts-mixed.js:108:5)
        at listOnTimeout (node:internal/timers:573:17)
        at process.processTimers (node:internal/timers:514:7) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v21.0.0-pre
  ...


Reason parallel/test-inspector-console
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49834, nodejs/node#49854)
Appeared test-ibm-rhel8-s390x-4, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54185/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54208/
Example
not ok 1825 parallel/test-inspector-console
  ---
  duration_ms: 15360.21300
  severity: fail
  exitcode: 1
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:46133/003a4f3d-092f-4ce6-a895-5cf94542924c
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] 
    Timed out waiting for matching notification (Runtime.consoleAPICalled)
    1
  ...


Reason parallel/test-inspector-debug-end
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49834, nodejs/node#49846)
Appeared test-osuosl-rhel8-ppc64_le-4, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54185/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54211/
Example
not ok 3066 parallel/test-inspector-debug-end
  ---
  duration_ms: 120083.91800
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    Test there's no crash stopping server that was not started
    Test there's no crash stopping server without connecting
    [err] Debugger listening on ws://127.0.0.1:44419/7c4fb3a8-ed0c-4cf0-8d83-d1e01c849cee
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    Test there's no crash stopping server after connecting
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:42913/356c2085-b71d-43de-b0ef-09f767d1bd61
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] 
  ...


Reason parallel/test-inspector-esm
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49834, nodejs/node#49756)
Appeared test-ibm-rhel8-s390x-1, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54185/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54219/
Example
not ok 1885 parallel/test-inspector-esm
  ---
  duration_ms: 15437.29600
  severity: fail
  exitcode: 1
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:44635/e0672c3d-b521-477b-9903-cee94eb1f180
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [test] Verifying debugger stops on start (--inspect-brk option)
    [err] Debugger attached.
    [err] 
    Timed out waiting for matching notification (break on file:///home/iojs/build/workspace/node-test-commit-linuxone/test/fixtures/es-modules/message.mjs:0)
    1
  ...


Reason parallel/test-inspector-multisession-ws
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49834, nodejs/node#49854)
Appeared test-ibm-rhel8-s390x-4, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54185/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54208/
Example
not ok 1870 parallel/test-inspector-multisession-ws
  ---
  duration_ms: 15463.85800
  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:45547/91806bdf-d356-4a85-8e2f-7c642fae7520
    [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 parallel/test-inspector-stop-profile-after-done
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49834, nodejs/node#49863)
Appeared test-osuosl-rhel8-ppc64_le-4, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54185/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54252/
Example
not ok 3191 parallel/test-inspector-stop-profile-after-done
  ---
  duration_ms: 120082.19500
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:43715/649e8bc3-3d90-45f7-95ba-33cf943d8a83
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] 
  ...


Reason parallel/test-runner-output
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49313, nodejs/node#49834)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-equinix-ubuntu2004_container-armv7l-1, undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/54184/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54185/
Example
not ok 2548 parallel/test-runner-output
  ---
  duration_ms: 411.14200
  severity: fail
  exitcode: 7
  stack: |-
    TAP version 13
    node:internal/test_runner/harness:50
          throw err;
          ^
    
    TypeError: _resolve is not a function
        at Duplexify.write [as _write] (node:internal/streams/duplexify:229:7)
        at writeOrBuffer (node:internal/streams/writable:447:12)
        at _write (node:internal/streams/writable:389:10)
        at Writable.write (node:internal/streams/writable:393:10)
        at TestsStream.ondata (node:internal/streams/readable:785:22)
        at TestsStream.emit (node:events:514:28)
        at Readable.read (node:internal/streams/readable:558:10)
        at flow (node:internal/streams/readable:1040:34)
        at resume_ (node:internal/streams/readable:1021:3)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
    
    Node.js v21.0.0-pre
  ...


Reason parallel/test-tick-processor-arguments
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49834, nodejs/node#49639)
Appeared test-equinix_mnx-smartos20-x64-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/54185/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54244/
Example
not ok 3666 parallel/test-tick-processor-arguments
  ---
  duration_ms: 300103.67600
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-worker-memory
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49745, nodejs/node#49756)
Appeared test-azure_msft-win2022_vs2019-x64-1, test-rackspace-win2019_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/54178/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54257/
Example
not ok 854 parallel/test-worker-memory
  ---
  duration_ms: 1397.00500
  severity: crashed
  exitcode: 3221225477
  stack: |-
    run() called with n=15 (numWorkers=4)
    run() called with n=15 (numWorkers=4)
    run() called with n=15 (numWorkers=4)
    run() called with n=15 (numWorkers=4)
    run() called with n=14 (numWorkers=4)
    run() called with n=14 (numWorkers=4)
    run() called with n=14 (numWorkers=4)
    run() called with n=14 (numWorkers=4)
    run() called with n=13 (numWorkers=4)
  ...


Reason pummel/test-crypto-timing-safe-equal-benchmarks
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49804, nodejs/node#48847)
Appeared test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/54212/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54250/
Example
not ok 3637 pummel/test-crypto-timing-safe-equal-benchmarks
  ---
  duration_ms: 7047.77200
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: timingSafeEqual should not leak information from its execution time (t=-9.038817440036503)
        at Object.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/pummel/test-crypto-timing-safe-equal-benchmarks.js:109:1)
        at Module._compile (node:internal/modules/cjs/loader:1429:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1487:10)
        at Module.load (node:internal/modules/cjs/loader:1261:32)
        at Module._load (node:internal/modules/cjs/loader:1077:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:99:12)
        at node:internal/main/run_main_module:23:47 {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      o...

Reason sequential/test-http-keepalive-maxsockets
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#49834, nodejs/node#49846)
Appeared test-ibm-aix72-ppc64_be-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54185/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54211/
Example
not ok 3966 sequential/test-http-keepalive-maxsockets
  ---
  duration_ms: 5706.68600
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    1 !== 2
    
        at Timeout._onTimeout (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix72-ppc64/test/sequential/test-http-keepalive-maxsockets.js:54:14)
        at listOnTimeout (node:internal/timers:573:17)
        at process.processTimers (node:internal/timers:514:7) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: 1,
      expected: 2,
      operator: 'strictEqual'
    }
    
    Node.js v21.0.0-pre
  ...


Jenkins Failure

Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 14 (nodejs/node#49759, nodejs/node#49654, nodejs/node#49313, nodejs/node#49834, nodejs/node#49854, nodejs/node#49804, nodejs/node#49799, nodejs/node#49857, nodejs/node#49756, nodejs/node#49642, nodejs/node#49859, nodejs/node#49846, nodejs/node#49750, nodejs/node#49847)
Appeared test-rackspace-win2022_vs2022-x64-6, test-rackspace-win2019_vs2019-x64-2, test-rackspace-win2019_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/54177/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54255/
Example
Build timed out (after 60 minutes). Marking the build as failed.

CCTest Failure

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 3 (nodejs/node#48847, nodejs/node#49834, nodejs/node#49846)
Appeared test-equinix-ubuntu2004_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1, test-osuosl-ubuntu2004_container-armv7l-1, test-osuosl-aix72-ppc64_be-3, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-equinix-ubuntu2004_container-arm64-2, test-equinix_mnx-smartos20-x64-3, test-equinix-ubuntu2004_sharedlibs_container-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/54174/
Last CI https://ci.nodejs.org/job/node-test-pull-request/54243/
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/jenkins3847193239390977207.sh
+ '[' -d .git ']'
+ git clean -fdx

Progress

  • parallel/test-inspector-scriptparsed-context (3)
  • parallel/test-tls-socket-close (3)
  • sequential/test-http-regr-gh-2928 (3)
  • sequential/test-net-connect-econnrefused (3)
  • sequential/test-perf-hooks (3)
  • parallel/test-cluster-fork-stdio (2)
  • parallel/test-fs-rmdir-recursive (2)
  • parallel/test-fs-write-stream-eagain (2)
  • parallel/test-http-server-request-timeouts-mixed (2)
  • parallel/test-inspector-console (2)
  • parallel/test-inspector-debug-end (2)
  • parallel/test-inspector-esm (2)
  • parallel/test-inspector-multisession-ws (2)
  • parallel/test-inspector-stop-profile-after-done (2)
  • parallel/test-runner-output (2)
  • parallel/test-tick-processor-arguments (2)
  • parallel/test-worker-memory (2)
  • pummel/test-crypto-timing-safe-equal-benchmarks (2)
  • sequential/test-http-keepalive-maxsockets (2)
  • Build timed out (after 60 minutes). Marking the build as failed. (14)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (3)
joyeecheung added a commit to nodejs/node that referenced this issue Sep 29, 2023
Previously when checking the initial timing we did a lot of checks
after accessing and copying timing.duration and before we check
that timing.duration is roughly the same as performance.now(),
which can lead to flakes if the overhead of the checking is
big enough. Update the test to check timing.duration against
performance.now() as soon as possible when it's copied instead
of computed.
:#

PR-URL: #49892
Refs: nodejs/reliability#676
Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
alexfernandez pushed a commit to alexfernandez/node that referenced this issue Nov 1, 2023
Previously when checking the initial timing we did a lot of checks
after accessing and copying timing.duration and before we check
that timing.duration is roughly the same as performance.now(),
which can lead to flakes if the overhead of the checking is
big enough. Update the test to check timing.duration against
performance.now() as soon as possible when it's copied instead
of computed.
:#

PR-URL: nodejs#49892
Refs: nodejs/reliability#676
Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
targos pushed a commit to nodejs/node that referenced this issue Nov 11, 2023
Previously when checking the initial timing we did a lot of checks
after accessing and copying timing.duration and before we check
that timing.duration is roughly the same as performance.now(),
which can lead to flakes if the overhead of the checking is
big enough. Update the test to check timing.duration against
performance.now() as soon as possible when it's copied instead
of computed.
:#

PR-URL: #49892
Refs: nodejs/reliability#676
Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
debadree25 pushed a commit to debadree25/node that referenced this issue Apr 15, 2024
Previously when checking the initial timing we did a lot of checks
after accessing and copying timing.duration and before we check
that timing.duration is roughly the same as performance.now(),
which can lead to flakes if the overhead of the checking is
big enough. Update the test to check timing.duration against
performance.now() as soon as possible when it's copied instead
of computed.
:#

PR-URL: nodejs#49892
Refs: nodejs/reliability#676
Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
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