-
Notifications
You must be signed in to change notification settings - Fork 13
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
Run all linting commands, even if some of them fail #1882
Conversation
Without the `ignore_errors` configuration option set to `True`, Tox exits as soon as any command in the list fails. In the case of the lint tests, we would like to continue running the commands, since they are essentially independent tests. This was masking formatting errors whenever the `check` command was failing, preventing us from knowing that we should fix those.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@brianhelba may also be interested in this, as we move towards integrating Ruff into the girder4/resonant stack.
Docs for this option
Thanks for mentioning the docs, @mvandenburgh; I forgot to mention that Note that some code formatting failures are shown in the CI for this branch; @marySalvi is going to push a fix for that in a separate PR, and I'll go ahead and merge this one now. |
@waxlamp @mvandenburgh Makes sense, especially for this one task, which is a read-only check where the steps aren't dependent on each other. |
🚀 PR was released in |
@brianhelba, is this enhancement on your radar for "upstreaming" to an eventual ruff-based Resonant cookiecutter? |
I don't think we'll add Codespell as an upstream recommendation. It seems to have too many false positives. I don't think it's necessary to run the format checks if the linting fails (since formatting shouldn't be fixed manually), but I'm happy to discuss it more in an upstream PR if someone wants to make it. |
Oh yes, I didn't mean to include Codespell in this.
Are you saying that (auto)formatting should only happen once linting passes? Aren't there cases where fixing the formatting would eliminate some (or maybe even all) linting errors? |
What upstream is the conversation about here? |
Resonant (formerly known as Girder 4). |
Without the
ignore_errors
configuration option set toTrue
, Tox exits as soon as any command in the list fails. In the case of the lint tests, we would like to continue running the commands, since they are essentially independent tests.This was masking formatting errors whenever the
check
command was failing, preventing us from knowing that we should fix those.(attn: @marySalvi)