Skip to content

Investigate workflow job failing on main: test / test (job 7) #103569

Closed as not planned

Description

@github-actions

🚨 Failure Summary 🚨:

  • 📋 Job Name: test / test (job 7)
  • 🔧 Failure in Workflow: Process new code merged to main
  • 🔗 Triggered by PR: PR Link
  • 👤 PR Author: @mkhutornyi
  • 🤝 Merged by: @marcaaron
  • 🐛 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.

👀 Please look into the following:

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

For detailed instructions, check this SO.

🐛 We appreciate your help in squashing this bug!

Activity

  1. mkhutornyi commented on Oct 9, 2026

    @mkhutornyi
    Contributor

    @MelvinBot investigate this. #103567 will fix this as well?

  2. MelvinBot commented on Oct 9, 2026

    @MelvinBot
    Contributor

    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 received undefined.

    Why it looks flaky:

    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

  3. mkhutornyi commented on Oct 9, 2026

    @mkhutornyi
    Contributor

    @MelvinBot which PR introduced flaky test?

  4. MelvinBot commented on Oct 9, 2026

    @MelvinBot
    Contributor

    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.

    Evidence

    view run

  5. grgia commented on Oct 12, 2026

    @grgia
    Contributor

    Same flaky test as #103714, fix in #103747. Closing as a dupe.

  6. melvin-bot commented on Oct 19, 2026

    @melvin-bot

    @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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions