Split volatile live-network specs out of PR CI gate#214
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
spectospec-stableand switches it to run only the deterministic/high-signal spec subset viamake spec-prspec-smoke.yml— a separate workflow that runs the full spec suite (make spec) on a daily schedule and viaworkflow_dispatch, covering the volatile live-network article/disease headings without blocking PRsSPEC_PR_DESELECT_ARGSblock) and inanalysis/technical/overview.mdThe six spec headings that were causing PR CI timeouts (article and disease retrieval against Europe PMC, PubTator, and MyDisease) are now excluded from the PR-blocking gate and covered by the dedicated smoke workflow instead.
Test plan
CI / spec-stablepasses on this PR (97 passed, 5 skipped, 7 deselected)tests/test_upstream_planning_analysis_docs.py) green (9 passed)Spec smoke (volatile live-network)to confirm the full-suite lane is visible and runnable