Skip to content

fix(e2e): update E2E tests workflow to sequential execution and fix r…#649

Merged
Wikid82 merged 2 commits intomainfrom
hotfix/ci
Feb 4, 2026
Merged

fix(e2e): update E2E tests workflow to sequential execution and fix r…#649
Wikid82 merged 2 commits intomainfrom
hotfix/ci

Conversation

@Wikid82
Copy link
Owner

@Wikid82 Wikid82 commented Feb 4, 2026

…ace conditions

  • Changed workflow name to reflect sequential execution for stability.
  • Reduced test sharding from 4 to 1 per browser, resulting in 3 total jobs.
  • Updated job summaries and documentation to clarify execution model.
  • Added new documentation file for E2E CI failure diagnosis.
  • Adjusted job summary tables to reflect changes in shard counts and execution type.

…ace conditions

- Changed workflow name to reflect sequential execution for stability.
- Reduced test sharding from 4 to 1 per browser, resulting in 3 total jobs.
- Updated job summaries and documentation to clarify execution model.
- Added new documentation file for E2E CI failure diagnosis.
- Adjusted job summary tables to reflect changes in shard counts and execution type.
@Wikid82 Wikid82 requested review from Copilot and removed request for Copilot February 4, 2026 16:08
@Wikid82 Wikid82 merged commit 2e3d53e into main Feb 4, 2026
2 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2026

❌ E2E Test Results: FAILED (Split Browser Jobs)

Some browser tests failed. Each browser runs independently.

Browser Results (Sequential Execution)

Browser Status Shards Execution
Chromium ⚠️ cancelled 1 Sequential
Firefox ❌ Failed 1 Sequential
WebKit ❌ Failed 1 Sequential

Phase 1 Hotfix Active: Each browser runs in a separate job. One browser failure does not block others.

📊 View workflow run & download reports


🤖 Phase 1 Emergency Hotfix - See docs/plans/browser_alignment_triage.md

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants