Skip to content

ci: add live test suite workflow - #681

Draft
0xisk wants to merge 1 commit into
mainfrom
ci/live-test-workflow
Draft

ci: add live test suite workflow#681
0xisk wants to merge 1 commit into
mainfrom
ci/live-test-workflow

Conversation

@0xisk

@0xisk 0xisk commented Jul 15, 2026

Copy link
Copy Markdown
Member

Types of changes

What types of changes does your code introduce to OpenZeppelin Midnight Contracts?

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Split out of #673 per review: the live CI workflow is large and complex, so it
lands on its own instead of alongside the test harness.

Stacked PR. Based on test/multisig-live-harness (#673), so the diff here
is just live.yml and its "Live tests in CI" CONTRIBUTING subsection. Once
#673 merges to main, this retargets to main automatically.

Adds .github/workflows/live.yml, which runs the live suite separately from
the required PR checks:

  • Nightly on main (regression net; a failure opens/comments a live-nightly tracking issue that auto-closes on the next green run).
  • On demand via workflow_dispatch, optionally scoped with category / filter inputs.
  • On a PR via the live-tests label.
  • A plan job reads the live-ready categories from the runner and fans out one job per category, each with its own stack and 6-hour job budget.
  • Never a required check.

PR Checklist

  • I have read the Contributing Guide
  • I have added tests that prove my fix is effective or that my feature works. N/A: CI workflow.
  • I have added documentation for new methods or changes to existing method behavior.
  • CI Workflows Are Passing

@0xisk
0xisk requested review from a team as code owners July 15, 2026 12:58
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 20b9a921-448c-44cc-9d27-0cd968111784

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/live-test-workflow

Comment @coderabbitai help to get the list of available commands.

@0xisk
0xisk marked this pull request as draft July 15, 2026 13:00
@0xisk 0xisk self-assigned this Jul 15, 2026
@0xisk
0xisk force-pushed the test/multisig-live-harness branch 2 times, most recently from a45bda7 to 7f6e09e Compare July 17, 2026 16:14
Base automatically changed from test/multisig-live-harness to main July 18, 2026 03:52
Run the live suite separately from the required PR checks: nightly on
`main`, on-demand dispatch, and via the `live-tests` PR label. A plan
job reads the live-ready categories from the runner and fans out one
job per category, each with its own stack and job budget. Documented
in the "Live tests in CI" CONTRIBUTING subsection.

Stacked on the live-harness branch (#673); rebases onto main once that
merges.

Refs: #673
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.

1 participant