Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip unit tests for docs-only changes #2226

Closed
nbiederbeck opened this issue Jan 19, 2023 · 1 comment · Fixed by #2227
Closed

Skip unit tests for docs-only changes #2226

nbiederbeck opened this issue Jan 19, 2023 · 1 comment · Fixed by #2227

Comments

@nbiederbeck
Copy link
Contributor

nbiederbeck commented Jan 19, 2023

Shall we try to reduce the CI time for documentation-only changes? I think of running just the docs CI when having the label documentation attached to the issue, and ignoring the whole pytest suite.

That would mean that we need to split our current pytest approach, where we test "normal" tests and documentation tests simultaneously.

This would greatly reduce the time to passing tests in minor (or large) documentation changes, and we would not be held up by increased memory usage, suddenly incompatible dependencies etc. like we were in the last few days.

(I'm thinking in particular of PRs like #2220)

@kosack
Copy link
Contributor

kosack commented Jan 19, 2023

Yes that would be fine - changes to the docs only should not require pytest to be run. And maybe it would encourage people to work more on the docs as well.

@maxnoe maxnoe changed the title Faster Docs CI ? Skip unit tests for docs-only changes Oct 21, 2023
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 a pull request may close this issue.

2 participants