[Due for payment 2025-11-20] [Due for payment 2025-11-10] [$125] Investigate workflow job failing on main: test / test (job 1)

[github-actions]

🚨 Failure Summary 🚨:

• 📋 Job Name: test / test (job 1)
• 🔧 Failure in Workflow: Process new code merged to main
• 🔗 Triggered by PR: PR Link
• 👤 PR Author: @kubabutkiewicz
• 🤝 Merged by: @mountiny
• 🐛 Error Message:
  failure: Process completed with exit code 1.

⚠️ Action Required ⚠️:

🛠️ A recent merge appears to have caused a failure in the job named test / test (job 1).
This issue has been automatically created and labeled with Workflow Failure for investigation.

👀 Please look into the following:

1. Why the PR caused the job to fail?
2. Address any underlying issues.

🐛 We appreciate your help in squashing this bug!

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021980944463555248994
• Upwork Job ID: 1980944463555248994
• Last Price Increase: 2025-11-17
• Automatic offers:
• PiyushChandra17 | Contributor | 109293170

Issue Owner

Current Issue Owner: @sakluger

[mountiny]

FAIL tests/ui/FloatingActionButtonTest.tsx
  ● Test suite failed to run

    A jest worker process (pid=2220) was terminated by another process: signal=SIGTERM, exitCode=null. Operating system logs may contain more information on why this occurred.

      at ChildProcessWorker._onExit (node_modules/jest-runner/node_modules/jest-worker/build/workers/ChildProcessWorker.js:370:23)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021980944463555248994

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts (External)

[mountiny]

This seems to have happened couple of times now on various tests, why are they not completing successfully?

[paulnjs]

🚨 Edited by proposal-police: This proposal was edited at 2025-10-22 10:49:49 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

Investigate workflow job failing on main: test / test (job 1)

What is the root cause of that problem?

A jest worker process (pid=2220) was terminated by another process: signal=SIGTERM, exitCode=null. Operating system logs may contain more information on why this occurred.

Jest worker processes, especially when running multiple tests in parallel, can consume significant memory. If the system or container runs out of memory, the operating system's OOM killer might terminate processes to free up resources.

What changes do you think we should make in order to solve the problem?

Following this ref, we can add --runInBand argument here to run all tests in serial. But also the test run slower

run: NODE_OPTIONS="$NODE_OPTIONS --experimental-vm-modules --max-old-space-size=4096" npm test -- --silent --shard=${{ fromJSON(matrix.chunk) }}/${{ strategy.job-total }} --runInBand --coverage --coverageDirectory=coverage/shard-${{ matrix.chunk }}

App/.github/workflows/test.yml

Line 46 in 487d9d4

run: NODE_OPTIONS="$NODE_OPTIONS --experimental-vm-modules" npm test -- --silent --shard=${{ fromJSON(matrix.chunk) }}/${{ strategy.job-total }} --max-workers ${{ steps.cpu-cores.outputs.count }} --coverage --coverageDirectory=coverage/shard-${{ matrix.chunk }}

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

undefined

What alternative solutions did you explore? (Optional)

We can reduce maxWorkers

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.