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 8) #94915
🐛 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.
The failure is a test timeout, not a code regression, and it's in a test suite your PR doesn't touch.
What failed:tests/ui/SessionTest.tsx → "Deep linking › should not remember the report path of the last deep link login after signing out and in again" — thrown: "Exceeded timeout of 240000 ms for a test." (job log).
Why it's unrelated to [Payment due @DylanDylann] [Odometer] Show discard changes modal when switching tabs #94899: Your PR is an Odometer / tab-switch / discard-changes feature. None of its changed files touch the auth/session/deep-link code or SessionTest.tsx. The failure is a timeout (slow/loaded CI runner), not an assertion failure pointing at changed behavior.
Known flaky:SessionTest is a documented flaky/slow suite (see [$250] Fix Flaky SessionTest #84927 "Fix Flaky SessionTest"), and this exact test / test (job 8) failure has recurred before. The test even carries an inline note that it "runs significantly longer than the suite default on loaded CI runners."
Closing as a flaky-test failure unrelated to the merged PR.
Activity
Julesssss commentedon Jun 30, 2026
@MelvinBot check if this was due to our changes. if not close this issue
Julesssss commentedon Jun 30, 2026
@MelvinBot check if this was due to our changes. If not you can close the issue
MelvinBot commentedon Jun 30, 2026
🤖 Not caused by your changes — closing.
The failure is a test timeout, not a code regression, and it's in a test suite your PR doesn't touch.
tests/ui/SessionTest.tsx→ "Deep linking › should not remember the report path of the last deep link login after signing out and in again" —thrown: "Exceeded timeout of 240000 ms for a test."(job log).SessionTest.tsx. The failure is a timeout (slow/loaded CI runner), not an assertion failure pointing at changed behavior.SessionTestis a documented flaky/slow suite (see [$250] Fix Flaky SessionTest #84927 "Fix Flaky SessionTest"), and this exacttest / test (job 8)failure has recurred before. The test even carries an inline note that it "runs significantly longer than the suite default on loaded CI runners."Closing as a flaky-test failure unrelated to the merged PR.