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
Investigate workflow job failing on main: test / test (job 6) #96968
🐛 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.
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:
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.
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.
Activity
David-2002065 commentedon Jul 24, 2026
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:PR #94814 only touches the Concierge side panel / report-actions code and its own unit tests:
src/components/SidePanel/SidePanelContextProvider.tsxsrc/hooks/useConciergeSidePanelReportActions.ts,useReportActionsVisibility.ts,useShouldSuppressConciergeIndicators.tsxsrc/libs/NetworkState.ts,ReportActionsUtils.ts,ReportUtils.ts,actions/Report/index.tssrc/pages/inbox/ConciergeSessionContext.tsxtests/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.David-2002065 commentedon Jul 24, 2026
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 inNewChatPageTest.tsx.Gonals commentedon Jul 24, 2026
All good