[Due for payment 2025-08-20] [$250] Investigate workflow job failing on main: test / test (job 3)

[github-actions]

🚨 Failure Summary 🚨:

• 📋 Job Name: test / test (job 3)
• 🔧 Failure in Workflow: Process new code merged to main
• 🔗 Triggered by PR: PR Link
• 👤 PR Author: @dangrous
• 🤝 Merged by: @lakchote
• 🐛 Error Message:
  failure: Process completed with exit code 1.
  warning: Cache not found for keys: Linux-jest

⚠️ Action Required ⚠️:

🛠️ A recent merge appears to have caused a failure in the job named test / test (job 3).
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/~021950714567077130370
• Upwork Job ID: 1950714567077130370
• Last Price Increase: 2025-07-31
• Automatic offers:
• nkdengineer | Contributor | 108259772

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @

[lakchote]

cc @mountiny looks like it's a flaky test

Same as

• Investigate workflow job failing on main: test / test (job 1) #62209 (comment)
• [Due for payment 2025-05-28] [$125] Investigate workflow job failing on main: test / test (job 1) #62169

[dangrous]

Seems like we should reopen that issue, though, since supposedly the fix was deployed?

[mountiny]

@lakchote seems like its a different test failing, I have not seen this one, could you please reopen this one and make it external?

[melvin-bot]

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

[melvin-bot]

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

[lorretheboy]

🚨 Edited by proposal-police: This proposal was edited at 2025-07-31 00:36:59 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 3) tests/unit/DateUtilsTest.ts

What is the root cause of that problem?

fetch is not being mocked in the Jest setup
DateUtils test is not setting up this mock, but when DateUtils is imported, it triggers Onyx connections that can lead to HTTP requests.

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

Need to mock it

import * as TestHelper from '../utils/TestHelper';
        global.fetch = TestHelper.getGlobalFetchMock();

App/tests/unit/DateUtilsTest.ts

Line 15 in e091028

beforeAll(() => {

Or can use like this (similar to other test) so that we will have better control whether we should pause or resume,...

    let mockFetch: MockFetch;
    beforeEach(() => {
        global.fetch = TestHelper.getGlobalFetchMock();
        mockFetch = fetch as MockFetch;
        return Onyx.clear().then(waitForBatchedUpdates);
    });

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

NA

What alternative solutions did you explore? (Optional)

NA

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.