You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Investigate workflow job failing on main: test / test (job 7) #103569
🐛 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 7).
🔍 This issue has been automatically created and labeled with Workflow Failure for investigation.
Failing test:IOURequestStepConfirmationPageTest › Report selection guard tests › should use the transaction report when it is allowed, even if it differs from the route (tests/ui/components/IOURequestStepConfirmationPageTest.tsx:1691). It expected "202" but received undefined.
Next step: You can close this issue as a flake. If it keeps failing, the likely cause is a race: the test presses Confirm before the page resolves report (IOURequestStepConfirmation.tsx:202-215). I haven't confirmed this by running the test. A fix would wait for the report to load before pressing Confirm.
I couldn't tie the flakiness to a recent PR. The test is old, and the same code that failed also passed in later runs, which points to a timing flake rather than a regression.
Between the last passing run (9e39920) and that failure, the only change was src/libs/PolicyUtils/permissions.ts plus its test. Neither touches the IOU confirmation page or this test.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.13-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
mkhutornyi commentedon Oct 9, 2026
@MelvinBot investigate this. #103567 will fix this as well?
MelvinBot commentedon Oct 9, 2026
No. [No QA][Failing Tests on Main] Fix the main typecheck and test failure in the self DM search test only fixes
OptionsListUtilsTest, which fails in job 5. Job 7 fails on a different test, and that test looks flaky rather than broken by Roll back orphaned transaction thread and surface the payment failure in the chat.Failing test:
IOURequestStepConfirmationPageTest › Report selection guard tests › should use the transaction report when it is allowed, even if it differs from the route(tests/ui/components/IOURequestStepConfirmationPageTest.tsx:1691). It expected"202"but receivedundefined.Why it looks flaky:
canAddTransaction.Next step: You can close this issue as a flake. If it keeps failing, the likely cause is a race: the test presses Confirm before the page resolves
report(IOURequestStepConfirmation.tsx:202-215). I haven't confirmed this by running the test. A fix would wait for the report to load before pressing Confirm.view run
mkhutornyi commentedon Oct 9, 2026
@MelvinBot which PR introduced flaky test?
MelvinBot commentedon Oct 9, 2026
I couldn't tie the flakiness to a recent PR. The test is old, and the same code that failed also passed in later runs, which points to a timing flake rather than a regression.
canAddTransactionspy (line 1630).Evidence
src/libs/PolicyUtils/permissions.tsplus its test. Neither touches the IOU confirmation page or this test.view run
grgia commentedon Oct 12, 2026
Same flaky test as #103714, fix in #103747. Closing as a dupe.
melvin-bot commentedon Oct 19, 2026
@marcaaron
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.13-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: