Skip to content

[Due for payment 2025-11-13] Investigate workflow job failing on main: test / test (job 1) #74333

Closed

Description

@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: @nkdengineer
  • 🤝 Merged by: @inimaga
  • 🐛 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!

Activity

  1. nkdengineer commented on Nov 5, 2025

    @nkdengineer
    Contributor

    Proposal

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

    Investigate workflow job failing on main: test / test

    What is the root cause of that problem?

    isWaitingOnBankAccount is random when creating a report when it's true

    isWaitingOnBankAccount: randBoolean(),

    App/tests/actions/IOUTest.ts

    Lines 6484 to 6489 in 2409bec

    const fakeReport: Report = {
    ...createRandomReport(1, undefined),
    type: CONST.REPORT.TYPE.EXPENSE,
    policyID: 'AA',
    stateNum: CONST.REPORT.STATE_NUM.SUBMITTED,
    statusNum: CONST.REPORT.STATUS_NUM.SUBMITTED,

    The check returns false here

    !iouReport?.isWaitingOnBankAccount &&

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

    We should override isWaitingOnBankAccount to false for the expense report here

    isWaitingOnBankAccount: false,
    

    App/tests/actions/IOUTest.ts

    Lines 6484 to 6489 in 2409bec

    const fakeReport: Report = {
    ...createRandomReport(1, undefined),
    type: CONST.REPORT.TYPE.EXPENSE,
    policyID: 'AA',
    stateNum: CONST.REPORT.STATE_NUM.SUBMITTED,
    statusNum: CONST.REPORT.STATUS_NUM.SUBMITTED,

    What alternative solutions did you explore? (Optional)

    We can remove isWaitingOnBankAccount from here then it will not be random

    isWaitingOnBankAccount: randBoolean(),

    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.

  2. nkdengineer commented on Nov 5, 2025

    @nkdengineer
    Contributor

    @inimaga It doesn't come from our PR.

  3. inimaga commented on Nov 5, 2025

    @inimaga
    Contributor

    You're right. Closing. Thanks for taking a look.

  4. nkdengineer commented on Nov 5, 2025

    @nkdengineer
    Contributor

    @inimaga I proposed a proposal for this? Can you take a look?

  5. inimaga commented on Nov 5, 2025

    @inimaga
    Contributor

    @nkdengineer I saw, but this workflow failure was introduced by this PR, and being worked on already by @mukhrr (See here and here).

    The convention is to assign the original PR authors to fix their regressions before opening it up to others.

  6. nkdengineer commented on Nov 5, 2025

    @nkdengineer
    Contributor

    Got it.

  7. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Nov 6, 2025
  8. changed the title [-]Investigate workflow job failing on main: test / test (job 1)[/-] [+][Due for payment 2025-11-13] Investigate workflow job failing on main: test / test (job 1)[/+] on Nov 6, 2025
  9. melvin-bot commented on Nov 6, 2025

    @melvin-bot

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

    If no regressions arise, payment will be issued on 2025-11-13. 🎊

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

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions