[Due for payment 2026-01-21] Investigate workflow job failing on main: test / test (job 2)

@jmusial

🚨 Failure Summary 🚨:

📋 Job Name: test / test (job 2)
🔧 Failure in Workflow: Process new code merged to main
🔗 Triggered by PR: PR Link
👤 PR Author: @jmusial
🤝 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 2).
This issue has been automatically created and labeled with Workflow Failure for investigation.

👀 Please look into the following:

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

🐛 We appreciate your help in squashing this bug!

Proposal

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

What is the root cause of that problem?

A test in IOUTest is flaky

App/tests/actions/IOUTest.ts

Lines 11784 to 11806 in 073940f

    
           it('should return timestamp from CREATED action when it exists', async () => { 
        
               const createdTimestamp = '2024-01-15 12:00:00.000'; 
        
               const report = createRandomReport(1, undefined); 
        
               const reportAction1 = createRandomReportAction(1); 
        
               const reportAction2 = { 
        
                   ...createRandomReportAction(2), 
        
                   actionName: CONST.REPORT.ACTIONS.TYPE.CREATED, 
        
                   created: createdTimestamp, 
        
               }; 
        
               const reportAction3 = createRandomReportAction(3); 
        
               await Onyx.multiSet({ 
        
                   [`${ONYXKEYS.COLLECTION.REPORT}${report.reportID}`]: report, 
        
                   [`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${report.reportID}`]: { 
        
                       [reportAction1.reportActionID]: reportAction1, 
        
                       [reportAction2.reportActionID]: reportAction2, 
        
                       [reportAction3.reportActionID]: reportAction3, 
        
                   }, 
        
               } as unknown as OnyxMultiSetInput); 
        
               await waitForBatchedUpdates(); 
        
               const result = getReportOriginalCreationTimestamp(report); 
        
               expect(result).toBe(createdTimestamp);

The helper createRandomReportAction random returns an action whose actionName is CREATED. Because getReportOriginalCreationTimestamp use Array.find to looks for the action with type CREATED (

App/src/libs/actions/IOU/index.ts

Line 9984 in 073940f

    
           const createdAction = Object.values(expenseReportActions ?? {}).find((action) => isCreatedAction(action));

), And the first report action type is random CREATED make the test fail.

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

We can swap reportAction1 and reportAction2 so that reportAction1's actionName is always CREATED, rather than reportAction2's

App/tests/actions/IOUTest.ts

Line 11787 in 073940f

const reportAction1 = createRandomReportAction(1);

const reportAction1={
              ...createRandomReportAction(1),
              actionName: CONST.REPORT.ACTIONS.TYPE.CREATED,
              created: createdTimestamp,
          };
          const reportAction2 = createRandomReportAction(2)
          const reportAction3 = createRandomReportAction(3);

Alternative we can override the generated action’s actionName with a deterministic, non-CREATED

   const reportAction1={
                ...createRandomReportAction(1),
                actionName: CONST.REPORT.ACTIONS.TYPE.ADD_COMMENT,
            };

What alternative solutions did you explore? (Optional)

We can apply both of the solutions above

Commented in offending PR

Fix flaky test in getReportOriginalCreationTimestamp

@situchan

Commented in offending PR

Thanks for the ping @situchan and thanks for investigation @linhvovan29546. I created a PR to fix this flaky test here

#79330

Reviewing label has been removed, please complete the "BugZero Checklist".

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.0-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

[NO QA] Fix flaky test in getReportOriginalCreationTimestamp #79330

If no regressions arise, payment will be issued on 2026-01-21. 🎊

Navigation Menu

Repository navigation

[Due for payment 2026-01-21] Investigate workflow job failing on main: test / test (job 2) #79215

Proposal

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

What is the root cause of that problem?

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

What alternative solutions did you explore? (Optional)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	it('should return timestamp from CREATED action when it exists', async () => {
	const createdTimestamp = '2024-01-15 12:00:00.000';
	const report = createRandomReport(1, undefined);
	const reportAction1 = createRandomReportAction(1);
	const reportAction2 = {
	...createRandomReportAction(2),
	actionName: CONST.REPORT.ACTIONS.TYPE.CREATED,
	created: createdTimestamp,
	};
	const reportAction3 = createRandomReportAction(3);

	await Onyx.multiSet({
	[`${ONYXKEYS.COLLECTION.REPORT}${report.reportID}`]: report,
	[`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${report.reportID}`]: {
	[reportAction1.reportActionID]: reportAction1,
	[reportAction2.reportActionID]: reportAction2,
	[reportAction3.reportActionID]: reportAction3,
	},
	} as unknown as OnyxMultiSetInput);
	await waitForBatchedUpdates();

	const result = getReportOriginalCreationTimestamp(report);
	expect(result).toBe(createdTimestamp);

[Due for payment 2026-01-21] Investigate workflow job failing on main: test / test (job 2) #79215

Description

Activity

linhvovan29546 commented on Jan 10, 2026

Proposal

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

What is the root cause of that problem?

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

What alternative solutions did you explore? (Optional)

situchan commented on Jan 11, 2026

hoangzinh commented on Jan 12, 2026

melvin-bot commented on Jan 14, 2026

melvin-bot commented on Jan 14, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions