ci: keep browser e2e out of normal pr path #1629

Merged

hongming merged 1 commits from fix/split-heavy-e2e-required-path into main 2026-05-21 04:15:09 +00:00

Conversation 2 Commits 1 Files Changed 3

+91 -11

core-devops commented 2026-05-21 04:02:54 +00:00

Member

Copy Link

Copy Source

SOP: follow-up to molecule-core#1357 for splitting heavyweight browser E2E out of the normal PR path.

Problem

• Branch protection only requires CI / all-required, but browser E2E workflows still execute on ordinary PR path changes and occupy scarce docker-host runners.
• e2e-chat is currently a known preexisting A2A DNS red, so running it on every relevant PR burns runner time without improving merge signal.

Change

• E2E Chat now runs heavy browser tests on push/main or staging, nightly schedule, workflow_dispatch, or PRs carrying merge-queue.
• E2E Staging Canvas now runs heavy browser tests on push/main, nightly schedule, workflow_dispatch, or PRs carrying merge-queue.
• Ordinary PRs still get the workflow context, but path-matching browser work no-ops unless the PR is queued.
• Added structural regression test to enforce workflow_dispatch, schedule, and merge-queue PR gating on both browser E2E workflows.

Verification

• python3 .gitea/scripts/lint-workflow-yaml.py --workflow-dir .gitea/workflows
• python3 -m pytest tests/test_lint_workflow_yaml.py tests/test_lint_required_context_exists_in_bp.py tests/test_lint_required_no_paths.py tests/test_heavy_e2e_pr_gating.py -q
• Result: 59 passed.

Expected saving

• Removes normal-PR browser E2E execution for canvas/workspace-server path changes unless PR is in merge-queue.
• Based on the previous observed PR run, this avoids roughly 17-20 minutes of e2e-chat runner occupancy and roughly 20 minutes of staging-canvas runner occupancy per matching ordinary PR.
• Coverage remains on merge-queue, push/main, nightly, and manual rerun paths.

Rollback

• Revert this PR to restore browser E2E execution on every matching PR.

SOP: follow-up to molecule-core#1357 for splitting heavyweight browser E2E out of the normal PR path. Problem - Branch protection only requires CI / all-required, but browser E2E workflows still execute on ordinary PR path changes and occupy scarce docker-host runners. - e2e-chat is currently a known preexisting A2A DNS red, so running it on every relevant PR burns runner time without improving merge signal. Change - E2E Chat now runs heavy browser tests on push/main or staging, nightly schedule, workflow_dispatch, or PRs carrying merge-queue. - E2E Staging Canvas now runs heavy browser tests on push/main, nightly schedule, workflow_dispatch, or PRs carrying merge-queue. - Ordinary PRs still get the workflow context, but path-matching browser work no-ops unless the PR is queued. - Added structural regression test to enforce workflow_dispatch, schedule, and merge-queue PR gating on both browser E2E workflows. Verification - python3 .gitea/scripts/lint-workflow-yaml.py --workflow-dir .gitea/workflows - python3 -m pytest tests/test_lint_workflow_yaml.py tests/test_lint_required_context_exists_in_bp.py tests/test_lint_required_no_paths.py tests/test_heavy_e2e_pr_gating.py -q - Result: 59 passed. Expected saving - Removes normal-PR browser E2E execution for canvas/workspace-server path changes unless PR is in merge-queue. - Based on the previous observed PR run, this avoids roughly 17-20 minutes of e2e-chat runner occupancy and roughly 20 minutes of staging-canvas runner occupancy per matching ordinary PR. - Coverage remains on merge-queue, push/main, nightly, and manual rerun paths. Rollback - Revert this PR to restore browser E2E execution on every matching PR.

core-devops added 1 commit 2026-05-21 04:02:54 +00:00

ci: keep browser e2e out of normal pr path 16b203fff1

hongming approved these changes 2026-05-21 04:15:08 +00:00

hongming left a comment

Owner

Copy Link

Copy Source

Approved via gitea-token per Hongming explicit bypass request for CI optimization follow-up.

Approved via gitea-token per Hongming explicit bypass request for CI optimization follow-up.

devops-engineer approved these changes 2026-05-21 04:15:08 +00:00

devops-engineer left a comment

Member

Copy Link

Copy Source

Approved via persona-devops-engineer-token per Hongming explicit bypass request for CI optimization follow-up.

Approved via persona-devops-engineer-token per Hongming explicit bypass request for CI optimization follow-up.

hongming merged commit e97eb95d9d into main 2026-05-21 04:15:09 +00:00

hongming referenced this issue from a commit 2026-05-21 04:15:11 +00:00

Merge pull request 'ci: keep browser e2e out of normal pr path' (#1629) from fix/split-heavy-e2e-required-path into main

core-devops referenced this pull request 2026-05-21 04:56:32 +00:00

[main-red] molecule-ai/molecule-core: 2ee97c097d #1627

Sign in to join this conversation.

Reviewers

No Reviewers

hongming

devops-engineer

Labels

Clear labels

area/ci

CI/CD pipeline issues

do-not-auto-merge

Opt out of autonomous merge-queue merging

kind/infrastructure

Infrastructure-related issues

merge-queue

Ready for serialized Gitea merge queue

merge-queue-hold

Temporarily hold PR in merge queue

platform/go

Go platform test issues

release-blocker

Blocks the staging→main promotion / a release

release-test

security

test-label-sre

tier:high

High risk per dev-sop §SOP-6 — ceo only, 24h cooldown

tier:low

Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve

tier:medium

Medium risk per dev-sop §SOP-6 — managers/ceo can approve

triage-test

test

wip

Work in progress — do not auto-merge

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)

No Assignees

3 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1629