-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Repeating pylint after failures. #612
Conversation
This surfaced as a false negative in googleapis#611.
The only issue I see here is that "real" lint failures will take twice as long, even if the envvars aren't set to try to speed the test up. |
But the user can always "Ctrl-C" and just go fix (if the watched pot is still boiling). If they aren't watching / waiting on the run, then the time isn't as crucial? |
Could we only retry on failure if we were doing a limited set to begin with? |
Yes, I'm happy to do that. I considered it but decided to go with the solution that involved less code. |
@tseaver I added a boolean indicating if a restricted fileset was used. PTAL. |
LGTM |
Repeating pylint after failures.
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
This surfaced as a false negative in #611.