-
Notifications
You must be signed in to change notification settings - Fork 170
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
Faster tests: Split out tests into separate backends and use altair 5.3.0 #2117
Conversation
Todo: |
@@ -16,6 +16,7 @@ | |||
from .linker_utils import _test_write_functionality, register_roc_data | |||
|
|||
|
|||
@mark_with_dialects_including("spark") |
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.
marked spark because otherwise this ran as part of core tests, which slowed down the core/duckdb tests significantly
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.
Great!
The aim of this PR is:
Results:
I have double checked the tests which run. The diff shows that this new structure runs (strictly) more tests than before, because previously we were not running
sqlite
marked tests anywhere. All previous tests are still run.Caching of poetry environments is now explicitly supported by the official setup-python action
I have now split out the tests as follows:
I have also upgraded to the latest altair (5.3.0) to make sure we use the performance improvements I did to alt.Chart.from_dict