Skip to content

ci: require the deterministic E2E suite on pull requests - #241

Open
zpzjzj wants to merge 1 commit into
mainfrom
ci/require-complete-e2e
Open

ci: require the deterministic E2E suite on pull requests#241
zpzjzj wants to merge 1 commit into
mainfrom
ci/require-complete-e2e

Conversation

@zpzjzj

@zpzjzj zpzjzj commented Sep 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • run the complete deterministic E2E suite in the required pull-request CI job instead of selecting test families by name
  • consistently gate live model and OpenSandbox tests behind SKILL_UP_FULL_E2E
  • use the mock engine for the eval-directory exclusion test so the required suite cannot consume a local CLI login
  • preserve the existing E2E Smoke check name for repository ruleset compatibility

Why

PR #233 added a static agent preflight that changed the invocation sequence of a stateful E2E fixture. TestEventLogSignalDuringBaselineReturnsNonZero detected the regression locally, but the required PR job only selected Pipeline, CLI, Contract, and NoneRuntime test names, so the event-log test was never run. PR #237 fixed that fixture; this change closes the CI coverage gap so new deterministic E2E test families are required automatically.

Live model, sandbox, Docker, and credential-backed checks remain explicit manual suites because they depend on secrets, quotas, and external services.

Verification

  • go test -tags e2e -timeout 1200s -count=1 -v ./e2e
  • make verify
  • make test
  • make test-action
  • make build

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 11, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-11T06:50:09.917199Z 7b7e1c3 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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