Conversation
…grows slow/integration markers (P-12/P-13)
The canonical Scheduled Tests template runs
``pytest -m "slow or integration"``. This repo's test suite has no
tests decorated with either marker, so pytest exits 5 ("no tests
collected") and the workflow has been failing on every nightly run
since the workflow landed.
Soften the run step to swallow exit-5 specifically — every other
non-zero exit is still preserved as failure, so a real test
regression once such tests exist will still surface. The schedule
will start exercising real tests automatically the first time a test
in this repo gets ``@pytest.mark.integration`` (the registered
marker in pyproject.toml).
Refs cross-repo CI audit, P-12 (juniper-data-client) /
P-13 (juniper-cascor-client) — both repos receive the identical fix.
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
1 participant
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.
This repo's Scheduled Tests workflow has been failing on every nightly run since it landed because the test suite has no tests marked `@pytest.mark.slow` or `@pytest.mark.integration` — `pytest -m "slow or integration"` exits 5 (no tests collected) and the workflow treats that as failure.
Soften the run step to swallow exit-5 specifically. Every other non-zero exit (real test failures, infrastructure errors) is still preserved.
Once this repo grows tests marked with either marker the schedule starts exercising them automatically — no further workflow change needed.
Refs cross-repo CI audit, P-12/P-13 (identical fix to data-client and cascor-client).