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
[Due for payment 2025-12-10] [$125] Fix flaky tests/actions/ReportTest.ts #76263
🐛 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.
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
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:
@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]
[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.
Activity
kacper-mikolajczak commentedon Nov 28, 2025
On it! 👀
kacper-mikolajczak commentedon Nov 28, 2025
Hmm looks like all the tests are passing on latest commit cfa8fde (history view). @mountiny let me know if this is still valid, thanks!
[-]Investigate workflow job failing on main: test / test (job 5)[/-][+]Fix flaky tests/actions/ReportTest.ts[/+][-]Fix flaky tests/actions/ReportTest.ts[/-][+][$250] Fix flaky tests/actions/ReportTest.ts[/+]melvin-bot commentedon Nov 28, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021994461870167175195
mountiny commentedon Nov 28, 2025
Seems like it is flaky
16 remaining items
[-][$125] Fix flaky tests/actions/ReportTest.ts[/-][+][Due for payment 2025-12-10] [$125] Fix flaky tests/actions/ReportTest.ts[/+]melvin-bot commentedon Dec 3, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 3, 2025
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:
melvin-bot commentedon Dec 3, 2025
@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]
sonialiap commentedon Dec 10, 2025
Payment summary:
@suneox $125 please request in NewDot. Please complete the checklist if applicable
@linhvovan29546 $125 paid in upwork ✔️
suneox commentedon Dec 10, 2025
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
sonialiap commentedon Dec 11, 2025
Thanks Cong!
garrettmknight commentedon Dec 18, 2025
$125 approved for @suneox