-
Notifications
You must be signed in to change notification settings - Fork 50
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.
Checks are passing so I have reason to believe the changes to the lint check worked.
But the check still took an inordinate amount of time.
Looking at the Actions log for this check, I see the linting step is taking over three minutes. Reviewing integration-tests.yml I have a few thoughts: You are using pipenv here to install pre-commit. I believe pre-commit sets up virtual envs itself. Within the log it says things like "this environment will be reused.." but really that's if you are running it locally. There is a GitHub Action for pre-commit that will set up a environment and cache it for you - reducing a good amount of runtime. If you really want to use pipenv, it looks like there is also a way to cache it and re-use it per run, which could also save you some execution time by skipping all the downloading and setup cycles. Within your |
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.
Apart from @kevholmes's fantastic ideas, this might help speed things along.
Linter check looks waay better @dhruvkb, 43 seconds - awesome! |
The speed improvements are very welcome @himanshu007-creator! I'm thinking of keeping #236 around to test if @kevholmes's suggestions (#237 (comment)) can improve the state of linting (and testing) further. |
Fixes
FixesAddresses #236Description
Technical details
Tests
Screenshots
Checklist
Update index.md
).main
ormaster
).Developer Certificate of Origin
Developer Certificate of Origin