nodejs / nodejs/reliability

CI Reliability 2024-07-16

Open
#922 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
57
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Failures in node-test-pull-request/60248 to node-test-pull-request/60341 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
2024-07-16 00:08 1 11 25 2 61 11.34%
Git Failure
Build Failure
Reason fatal: No rebase in progress?
Type BUILD_FAILURE
Failed PR 6 (https://github.com/nodejs/node/pull/53628/, https://github.com/nodejs/node/pull/53590/, https://github.com/nodejs/node/pull/53803/, https://github.com/nodejs/node/pull/53619/, https://github.com/nodejs/node/pull/53853/, https://github.com/nodejs/node/pull/53725/)
Appeared test-orka-macos10.15-x64-2, test-ibm-ubuntu2204_sharedlibs_container-x64-4, test-ibm-ubuntu2204_sharedlibs_container-x64-2, test-equinix-ubuntu2004_container-arm64-2, test-mnx-ubuntu2204-x64-1, test-ibm-ubuntu2204_sharedlibs_container-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/60252/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60339/
Example
fatal: No rebase in progress?

Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53619/, https://github.com/nodejs/node/pull/53464/)
Appeared test-equinix-ubuntu2004_sharedlibs_container-arm64-5, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu2004_container-armv7l-2
First CI https://ci.nodejs.org/job/node-test-pull-request/60293/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60298/
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

JSTest Failure
Reason parallel/test-net-write-fully-async-buffer
Type JS_TEST_FAILURE
Failed PR 8 (https://github.com/nodejs/node/pull/53814/, https://github.com/nodejs/node/pull/53617/, https://github.com/nodejs/node/pull/53627/, https://github.com/nodejs/node/pull/53812/, https://github.com/nodejs/node/pull/53803/, https://github.com/nodejs/node/pull/53820/, https://github.com/nodejs/node/pull/53704/, https://github.com/nodejs/node/pull/53657/)
Appeared test-equinix_mnx-smartos20-x64-3, test-equinix_mnx-smartos20-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/60248/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60332/
Example
not ok 3829 parallel/test-net-write-fully-async-buffer
  ---
  duration_ms: 300146.05500
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason sequential/test-http-server-request-timeouts-mixed
Type JS_TEST_FAILURE
Failed PR 8 (https://github.com/nodejs/node/pull/53812/, https://github.com/nodejs/node/pull/53814/, https://github.com/nodejs/node/pull/53619/, https://github.com/nodejs/node/pull/53803/, https://github.com/nodejs/node/pull/53838/, https://github.com/nodejs/node/pull/53841/, https://github.com/nodejs/node/pull/53823/, https://github.com/nodejs/node/pull/53725/)
Appeared test-orka-macos11-x64-1, test-orka-macos11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/60260/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60339/
Example
not ok 4147 sequential/test-http-server-request-timeouts-mixed
  ---
  duration_ms: 3252.03300
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:408
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
    
      assert(request2.completed)
    
        at Timeout._onTimeout (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/sequential/test-http-server-request-timeouts-mixed.js:108:5)
        at listOnTimeout (node:internal/timers:601:17)
        at process.processTimers (node:internal/timers:539:7) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v23.0.0-pre
  ...


Reason parallel/test-dns
Type JS_TEST_FAILURE
Failed PR 6 (https://github.com/nodejs/node/pull/53627/, https://github.com/nodejs/node/pull/53617/, https://github.com/nodejs/node/pull/53659/, https://github.com/nodejs/node/pull/53842/, https://github.com/nodejs/node/pull/53838/, https://github.com/nodejs/node/pull/53823/)
Appeared test-ibm-ubuntu2204_sharedlibs_container-x64-1, test-equinix-ubuntu2004_container-arm64-2, test-rackspace-fedora32-x64-1, test-osuosl-rhel8-ppc64_le-2, test-azure_msft-win11_vs2022-arm64-3, test-osuosl-rhel9-ppc64_le-3, test-ibm-ubuntu2204_sharedlibs_container-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/60259/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60314/
Example
not ok 934 parallel/test-dns
  ---
  duration_ms: 140.79600
  severity: fail
  exitcode: 1
  stack: |-
    (node:2882386) [DEP0118] DeprecationWarning: The provided hostname "" is not a valid hostname, and is supported in the dns module solely for compatibility.
    (Use `node --trace-deprecation ...` to show where the warning was created)
    node:assert:126
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
    + actual - expected ... Lines skipped
    
      [
        {
          address: '1.2.3.4',
    +     ttl: 3333333332,
    -     ttl: 3333333333,
          type: 'A'
        },
        {
          address: '::42',
    +     ttl: 3333333332,
    -     ttl: 3333333333,
          type: 'AAAA'
    ...


Reason wpt/test-compression
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/53619/, https://github.com/nodejs/node/pull/53803/, https://github.com/nodejs/node/pull/53849/)
Appeared test-digitalocean-ubuntu2204_sharedlibs_container-x64-4, test-digitalocean-ubuntu2204_sharedlibs_container-x64-7, test-digitalocean-ubuntu2204_sharedlibs_container-x64-10
First CI https://ci.nodejs.org/job/node-test-pull-request/60293/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60333/
Example
not ok 4111 wpt/test-compression
  ---
  duration_ms: 1440109.44500
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    [SKIPPED] compression-bad-chunks.tentative.any.js: Execution "hangs", ArrayBuffer and TypedArray is not accepted and throws, instead of rejects during writer.write
    [SKIPPED] decompression-bad-chunks.tentative.any.js: Execution "hangs", ArrayBuffer and TypedArray is not accepted and throws, instead of rejects during writer.write
    [SKIPPED] decompression-buffersource.tentative.any.js: ArrayBuffer and TypedArray is not accepted and throws, instead of rejects during writer.write
    [SKIPPED] idlharness-shadowrealm.window.js: ShadowRealm support is not enabled
    [SKIPPED] third_party/pako/pako_inflate.min.js: This is not a test file.
    [PASS] "a" should cause the constructor to throw
    [PASS] no input should cause the constructor to throw
    [PASS] non-string input should cause the constructor to throw
    [PASS] "a" should cause the constructor to throw
    [PASS] no inpu...

Reason parallel/test-file-write-stream4
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53617/, https://github.com/nodejs/node/pull/53614/)
Appeared test-equinix-ubuntu2004_container-arm64-2, test-equinix-rhel8_container-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/60265/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60277/
Example
not ok 4011 parallel/test-file-write-stream4
  ---
  duration_ms: 360107.49700
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-fs-watch-recursive-delete
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53590/, https://github.com/nodejs/node/pull/53659/)
Appeared test-equinix-ubuntu2004_container-armv7l-1, test-digitalocean-fedora37-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/60278/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60282/
Example
not ok 1022 parallel/test-fs-watch-recursive-delete
  ---
  duration_ms: 838.63100
  severity: fail
  exitcode: 1
  stack: |-
    Mismatched <anonymous> function calls. Expected at least 1, actual 0.
        at Proxy.mustCallAtLeast (/home/iojs/build/workspace/node-test-binary-armv7l/test/common/index.js:457:10)
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-binary-armv7l/test/parallel/test-fs-watch-recursive-delete.js:21:29)
        at Module._compile (node:internal/modules/cjs/loader:1505:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1589:10)
        at Module.load (node:internal/modules/cjs/loader:1283:32)
        at Module._load (node:internal/modules/cjs/loader:1099:12)
        at TracingChannel.traceSync (node:diagnostics_channel:315:14)
        at wrapModuleLoad (node:internal/modules/cjs/loader:216:24)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:158:5)
  ...


Reason parallel/test-performance-function
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53659/, https://github.com/nodejs/node/pull/53619/)
Appeared undefined, test-ibm-rhel8-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/60271/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60293/
Example
not ok 2455 parallel/test-performance-function
  ---
  duration_ms: 334.04700
  severity: fail
  exitcode: 1
  stack: |-
    
    node:internal/event_target:1090
      process.nextTick(() => { throw err; });
                               ^
    RangeError [ERR_OUT_OF_RANGE]: The value of "val" is out of range. It must be >= 1 && <= 9007199254740991. Received 0
        at RecordableHistogram.record (node:internal/histogram:291:5)
        at processComplete (node:internal/perf/timerify:40:15)
        at timerified m (node:internal/perf/timerify:87:5)
        at /home/iojs/build/workspace/node-test-commit-custom-suites-freestyle/test/parallel/test-performance-function.js:103:5 {
      code: 'ERR_OUT_OF_RANGE'
    }
    
    Node.js v23.0.0-pre
  ...


Reason parallel/test-sqlite
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53590/, https://github.com/nodejs/node/pull/53842/)
Appeared test-osuosl-rhel8-ppc64_le-2
First CI https://ci.nodejs.org/job/node-test-pull-request/60278/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60295/
Example
not ok 3823 parallel/test-sqlite
  ---
  duration_ms: 120365.11500
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    TAP version 13
    # Subtest: accessing the node:sqlite module
        # Subtest: cannot be accessed without the node: scheme
        ok 1 - cannot be accessed without the node: scheme
          ---
          duration_ms: 2.97222
          ...


Reason pummel/test-hash-seed
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53832/, https://github.com/nodejs/node/pull/53803/)
Appeared test-ibm-rhel8-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/60286/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60290/
Example
not ok 3831 pummel/test-hash-seed
  ---
  duration_ms: 66000.39700
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/errors:983
      const err = new Error(message);
                  ^
    
    Error: Command failed: /home/iojs/build/workspace/node-test-commit-linux/out/Release/node --allow-natives-syntax /home/iojs/build/workspace/node-test-commit-linux/test/fixtures/guess-hash-seed.js
    /home/iojs/build/workspace/node-test-commit-linux/test/fixtures/guess-hash-seed.js:163
      throw new Error('no candidates remaining');
      ^
    
    Error: no candidates remaining
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux/test/fixtures/guess-hash-seed.js:163:9)
        at Module._compile (node:internal/modules/cjs/loader:1505:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1589:10)
        at Module.load (node:internal/modules/cjs/loader:1283:32)
        at Module._load (node:internal/modules/cjs/loader:1099:12)
        at TracingChannel.traceS...

Reason sequential/test-single-executable-application-empty
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/53605/, https://github.com/nodejs/node/pull/53619/)
Appeared test-azure_msft-win10_vs2019-x64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/60254/
Last CI https://ci.nodejs.org/job/node-test-pull-request/60293/
Example
not ok 990 sequential/test-single-executable-application-empty
  ---
  duration_ms: 121007.37800
  severity: fail
  exitcode: 1
  stack: |-
    timeout
    Copied c:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe to c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.989\sea.exe
  ...


Progress
  • fatal: No rebase in progress? (6)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • parallel/test-net-write-fully-async-buffer (8)
  • sequential/test-http-server-request-timeouts-mixed (8)
  • parallel/test-dns (6)
  • wpt/test-compression (3)
  • parallel/test-file-write-stream4 (2)
  • parallel/test-fs-watch-recursive-delete (2)
  • parallel/test-performance-function (2)
  • parallel/test-sqlite (2)
  • pummel/test-hash-seed (2)
  • sequential/test-single-executable-application-empty (2)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the generated reliability report and the linked CI console logs, especially the failures for parallel/test-net-write-fully-async-buffer, sequential/test-http-server-request-timeouts-mixed, parallel/test-dns, and wpt/test-compression. Compare repeated failures across the listed jobs and identify whether each is a test or infrastructure problem. Done requires an agreed fix or follow-up for the recurring failures and evidence that the affected CI jobs pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, javascript, nodejs, shell
Domain
ci-cd, devops, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.