-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Use incremental mode in python evaluation test cases #1412
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
I looked into this for a few minutes and one problem is that currently each test is run in a clean directory. There currently is no way to change the name of the cache directory, and it's always |
I just tried making the pythoneval tests use a shared cache directory via this diff:
However I get a failure (consistently) with:
this appears to be an incremental bug? |
Yes, it looks like name of a method is lost during (de-)serialisation. If you have time and desire, you could fix this yourself, otherwise create a separate issue about this. |
@ilevkivskyi that makes sense. I'm afraid I'm not familiar enough with the intricacies of incremental to debug this one. I'll bump the priority of that issue up however. |
This causes the tests to run much faster! On my machine without incremental they take 52 seconds. With the incremental cache, they take only 22 seconds. This fixes #1412.
The Python evaluation test cases (which don't actually run the code if there are type errors...) use full stubs for
builtins
andtyping
. Using incremental mode would likely speed them up significantly, as processing stubs probably takes the majority of time. These tests are the long pole in the full test suite, so this could give a nice speed boost.The text was updated successfully, but these errors were encountered: