-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
CI: Exclude asv benchmark envs from flake8 checks #23497
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
Conversation
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.
can u move these to the setup.cfg section instead
@jreback Done |
Codecov Report
@@ Coverage Diff @@
## master #23497 +/- ##
=======================================
Coverage 92.23% 92.23%
=======================================
Files 161 161
Lines 51197 51197
=======================================
Hits 47220 47220
Misses 3977 3977
Continue to review full report at Codecov.
|
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.
lgtm
You could add a comment too, something like env # directory created by asv after a run
. Not being in the repo, we may have the temptation to delete it later on
@datapythonista Done |
thanks @qwhelan |
When running
ci/code_checks.sh
on a local repository that has also been used to runasv
benchmarks,flake8
also lints the environments created. This massively increases the runtime and leads to linting errors on non-pandas
packages, which is not informative.This change simply adds
env
to theflake8
exclude list, which resolves the issue seen above.Before
After
Output comparison