Skip to content

[Due for payment 2026-06-25] [$250] Investigate workflow job failing on main: test / test (job 8) #93754

Closed

Description

@github-actions

🚨 Failure Summary 🚨:

  • 📋 Job Name: test / test (job 8)
  • 🔧 Failure in Workflow: Process new code merged to main
  • 🔗 Triggered by PR: PR Link
  • 👤 PR Author: @MelvinBot
  • 🤝 Merged by: @youssef-lr
  • 🐛 Error Message:
    warning: [git-mirror] Skipping cache commit: Found 2 failed/cancelled steps
    warning: [git-mirror] - Step: unknown (failed)
    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 8).
🔍 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!

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @ahmedGaber93

Activity

  1. ahmedGaber93 commented on Jun 16, 2026

    @ahmedGaber93
    Contributor

    @MelvinBot please create new PR to fix this https://github.com/Expensify/App/actions/runs/27651654084/job/81776821001, it looks we missed to pass OnyxListItemProvider warpper.

  2. MelvinBot commented on Jun 16, 2026

    @MelvinBot
    Contributor

    🤖 Draft PR created: #93759
    Please mark it as "Ready for review" when it is ready for review.

    What was fixed: tests/unit/hooks/useSearchBulkActionsExportTest.ts was missing the OnyxListItemProvider wrapper on its two renderHook(() => useSearchBulkActions(...)) calls, which is why the test (job 8) check failed with useOnyxContext must be used within a OnyxListItemProvider [key: session]. Adding the wrapper surfaced a second latent gap — the test's @libs/SearchUIUtils mock omitted getValidGroupBy (now called by the hook) — so I added a faithful mock for it as well. Both tests pass locally.

  3. changed the title [-]Investigate workflow job failing on main: test / test (job 8)[/-] [+][$250] Investigate workflow job failing on main: test / test (job 8)[/+] on Jun 16, 2026
  4. melvin-bot commented on Jun 16, 2026

    @melvin-bot
  5. changed the title [-][$250] Investigate workflow job failing on main: test / test (job 8)[/-] [+][Due for payment 2026-06-25] [$250] Investigate workflow job failing on main: test / test (job 8)[/+] on Jun 18, 2026
  6. melvin-bot commented on Jun 18, 2026

    @melvin-bot

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

  7. melvin-bot commented on Jun 18, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.14-1 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 2026-06-25. 🎊

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

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions