Skip to content

[Due for payment 2025-12-10] [$125] Fix flaky tests/actions/ReportTest.ts #76263

Closed

Description

@github-actions

🚨 Failure Summary 🚨:

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

⚠️ Action Required ⚠️:

🛠️ A recent merge appears to have caused a failure in the job named test / test (job 5).
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/~021994461870167175195
  • Upwork Job ID: 1994461870167175195
  • Last Price Increase: 2025-11-28
  • Automatic offers:
    • linhvovan29546 | Contributor | 109655526
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @sonialiap

Activity

  1. kacper-mikolajczak commented on Nov 28, 2025

    @kacper-mikolajczak
    Contributor

    On it! 👀

  2. kacper-mikolajczak commented on Nov 28, 2025

    @kacper-mikolajczak
    Contributor

    Hmm looks like all the tests are passing on latest commit cfa8fde (history view). @mountiny let me know if this is still valid, thanks!

  3. changed the title [-]Investigate workflow job failing on main: test / test (job 5)[/-] [+]Fix flaky tests/actions/ReportTest.ts[/+] on Nov 28, 2025
  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed on Nov 28, 2025
  5. changed the title [-]Fix flaky tests/actions/ReportTest.ts[/-] [+][$250] Fix flaky tests/actions/ReportTest.ts[/+] on Nov 28, 2025
  6. melvin-bot commented on Nov 28, 2025

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 28, 2025
  8. mountiny commented on Nov 28, 2025

    @mountiny
    Contributor

    Seems like it is flaky

  9. 16 remaining items

  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 3, 2025
  11. changed the title [-][$125] Fix flaky tests/actions/ReportTest.ts[/-] [+][Due for payment 2025-12-10] [$125] Fix flaky tests/actions/ReportTest.ts[/+] on Dec 3, 2025
  12. melvin-bot commented on Dec 3, 2025

    @melvin-bot

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

  13. melvin-bot commented on Dec 3, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.70-0 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-12-10. 🎊

    For reference, here are some details about the assignees on this issue:

  14. melvin-bot commented on Dec 3, 2025

    @melvin-bot

    @suneox / @linhvovan29546 @sonialiap The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  15. sonialiap commented on Dec 10, 2025

    @sonialiap
    Contributor

    Payment summary:
    @suneox $125 please request in NewDot. Please complete the checklist if applicable
    @linhvovan29546 $125 paid in upwork ✔️

  16. suneox commented on Dec 10, 2025

    @suneox
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: https://github.com/Expensify/App/pull/67193/files#r2607273758

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

      N/A: cause it isn't an impactful bug without QA

  17. sonialiap commented on Dec 11, 2025

    @sonialiap
    Contributor

    Thanks Cong!

  18. garrettmknight commented on Dec 18, 2025

    @garrettmknight
    Contributor

    $125 approved for @suneox

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorWorkflow Failure

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions