Skip to content

Investigate workflow job failing on main: test / test (job 6) #96968

Closed

Description

@github-actions

🚨 Failure Summary 🚨:

  • 📋 Job Name: test / test (job 6)
  • 🔧 Failure in Workflow: Process new code merged to main
  • 🔗 Triggered by PR: PR Link
  • 👤 PR Author: @dilshodmackbook-sketch
  • 🤝 Merged by: @Gonals
  • 🐛 Error Message:
    warning: [git-mirror] Skipping cache commit: Found 2 failed/cancelled steps
    warning: [git-mirror] - Step: unknown (failed)
    warning: Skipping sticky disk commit due to previous step failures
    warning: - Step: unknown (failed)
    warning: Found 2 failed/cancelled steps in previous workflow steps
    warning: Skipping sticky disk commit due to previous step failures
    warning: - Step: unknown (failed)
    warning: Found 2 failed/cancelled steps in previous workflow steps
    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 6).
🔍 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. David-2002065 commented on Jul 24, 2026

    @David-2002065
    Contributor

    This looks like an unrelated flaky failure rather than a regression from PR #94814.

    The failing test is tests/ui/NewChatPageTest.tsx → NewChatPage › should not display "Add to group" button on expensify emails › accountspayable@expensify.com, failing with:

    Unable to find an element with accessibility label: accountspayable@expensify.com
    

    PR #94814 only touches the Concierge side panel / report-actions code and its own unit tests:

    • src/components/SidePanel/SidePanelContextProvider.tsx
    • src/hooks/useConciergeSidePanelReportActions.ts, useReportActionsVisibility.ts, useShouldSuppressConciergeIndicators.tsx
    • src/libs/NetworkState.ts, ReportActionsUtils.ts, ReportUtils.ts, actions/Report/index.ts
    • src/pages/inbox/ConciergeSessionContext.tsx
    • tests under tests/unit/...

    None of it is related to the New Chat page or how its participant rows render. The failure is a render lookup that timed out (the suite ran ~103s before the query gave up), which is the usual signature of a flaky timeout, not a logic break introduced by this PR.

    Re-running test (job 6) should confirm it passes. Happy to help dig further if it turns out to be consistently reproducible.

  2. David-2002065 commented on Jul 24, 2026

    @David-2002065
    Contributor

    I tried to re-run test (job 6) myself but I don't have the repo permissions for it (Must have admin rights to Repository). @Gonals could you re-run the failed job on run 30098743157? I expect it to pass and confirm this was just a flaky timeout in NewChatPageTest.tsx.

  3. Gonals commented on Jul 24, 2026

    @Gonals
    Contributor

    All good

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