-
-
Notifications
You must be signed in to change notification settings - Fork 933
Performance regression on travis #245
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
Comments
It seems that all that time is spend in rev-parse. The latter might trigger plenty of file accesses, but it's still the question why this is so much slower in py3 all of the sudden. |
Hoping to make this significantly faster on travis. Related to #245
Performance regression is still visible on travis, even though said rev-parse test was nerfed to the point where we save 2 or 3 minutes at least. However, there must be more slow tests that need to be handled somehow. |
This seems to be gone ! |
Py3 runs are 3 to 6 times slower on travis, even though this doesn't show on my machine at all.
What's up with that ?
The text was updated successfully, but these errors were encountered: