-
Notifications
You must be signed in to change notification settings - Fork 16
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
Pylint takes almost two hours?! #215
Comments
I just ran it locally with
No idea what might make it do that on the CI, but it is very funny 😁 |
Maybe out of memory, like the rest of it? |
Hm, it seems to take about 3-400MB per job on my machine (4 jobs total), so comfortably within CI limits.. As far as I can tell, pylint also doesn't keep any caches (besides some stats to show the |
3h is apparently not out of the question? 😱 #217 (comment) |
On Gitlab it seems to take the usual amount of time (with presumably the same library versions?) |
@inducer Following @matthiasdiener excellent point in inducer/grudge#317 (comment), I thought that maybe pytential is doing the same thing. That seems to indeed be the case! For the
while for the standard
So pretty much all of the runtime of the |
E.g. here: https://github.com/inducer/pytential/actions/runs/5675790498/job/15397715698
It's the longest-running of all the CI jobs. 🤔 If it keeps this up, I might nuke it.
The text was updated successfully, but these errors were encountered: