Skip to content

ci: run the property-tests branch's property tests nightly - #2897

Draft
tonyandrewmeyer wants to merge 4 commits into
canonical:mainfrom
tonyandrewmeyer:property-tests-nightly
Draft

tonyandrewmeyer wants to merge 4 commits into
canonical:mainfrom
tonyandrewmeyer:property-tests-nightly

Conversation

@tonyandrewmeyer

Copy link
Copy Markdown
Collaborator

GitHub only runs scheduled workflows from the default branch, so the nightly run of the Hypothesis property tests on the property-tests branch (#2869) has to live on main. This adds property-tests-nightly.yaml, which checks out property-tests, runs tox -e property with the nightly profile, and opens or updates an issue when a scheduled run fails, through notify-scheduled-failure.yaml like the other scheduled workflows.

This needs #2869 to land first: until then property-tests has no property tox environment, so the nightly run would fail.

tonyandrewmeyer and others added 2 commits November 12, 2026 15:32
The property tests live on the long-lived property-tests branch, and
GitHub only schedules workflows from the default branch. This workflow
checks that branch out every night and runs the tests with the nightly
Hypothesis profile, opening an issue if they fail.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
property-tests is only merged from main by hand, so on its own the
nightly run would test whatever main was at the last merge. Merging
main in the checkout, without committing, tests the current code, and
a conflict fails the run to say the branch needs merging.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tonyandrewmeyer tonyandrewmeyer changed the title ci: run the property tests nightly against the property-tests branch ci: run the property-tests branch's property tests nightly Nov 13, 2026
tonyandrewmeyer and others added 2 commits November 14, 2026 11:34
A hang in setup or the merge would otherwise run to the 360-minute job
default.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A conflict and a property failure open the same scheduled-failure issue,
but need different fixes. An error annotation puts the reason at the top
of the run, where the failure enrichment will also see it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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