nodejs / nodejs/node

Various AIX tests pass on Node 22, fail on later supported versions

Open
#61,657 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
122k
Forks
37.3k
Avg merge
4d 2h
Merged PRs (30d)
283

Description

A sibling issue to https://github.com/nodejs/node/issues/61441
After clearing up some of the flakiness and machine-specific problems that were occurring on AIX it became noticable that there were some failures that were NOT failing when run against Node 22.

This issue is to continue the analysis and determine if the failures are from changes in the test cases or functional changes in the Node that caused the intermittent failures in later releases.

The RUN_TESTS parameter of the stress test that I was using to experiment with is sequential/test-watch-mode-restart-esm-loading-error wpt/test-streams async-hooks/test-emit-after-on-destroyed node-api/test_threadsafe_function parallel/test-repl-preview - The test-emit-after-destroyed one is a reasonably common flake on AIX and has been marked as such. wpt/test-streams is the other one that shows a slightly lower failure rate (around 1%) on the later versions.

Sample runs showing the differences - each of these ran 100 times on each of four AIX machines:

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 by running the listed RUN_TESTS cases repeatedly on AIX against Node 22 and later supported versions, using the linked stress-test results as comparison. Inspect sequential/test-watch-mode-restart-esm-loading-error, wpt/test-streams, async-hooks/test-emit-after-on-destroyed, node-api/test_threadsafe_function, and parallel/test-repl-preview. Done means determining whether each difference comes from test changes or functional changes in Node, while separating known AIX flakes.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
operating-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.