Skip to content
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

Merged
merged 11 commits into from
Apr 3, 2024

Conversation

RobinL
Copy link
Member

@RobinL RobinL commented Mar 29, 2024

The aim of this PR is:

  • to make the overall test suite run faster
  • to run the full duckdb + core tests as fast as possible to speed up finding test failures (to make iterating faster)

Results:

  • Duckdb and core tests now run in 1m 32s rather than 5m 3s
  • Slowest test is now 3m 13s rather than 5m 3s

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:

  • core and duckdb (these all use duckdb where a backend is needed)
  • postgres
  • spark and sqlite

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

@RobinL RobinL changed the title (WIP) Split out tests into separate backends Faster tests: Split out tests into separate backends and use altair 5.3.0 Mar 30, 2024
@RobinL RobinL requested a review from ADBond March 30, 2024 17:55
@RobinL
Copy link
Member Author

RobinL commented Mar 30, 2024

Todo:
Double check the full list of tests running to check we haven't missed any

@@ -16,6 +16,7 @@
from .linker_utils import _test_write_functionality, register_roc_data


@mark_with_dialects_including("spark")
Copy link
Member Author

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

Copy link
Contributor

@ADBond ADBond left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great!

@ADBond ADBond linked an issue Apr 2, 2024 that may be closed by this pull request
@RobinL RobinL merged commit 4402316 into splink4_dev Apr 3, 2024
15 checks passed
@RobinL RobinL deleted the split_out_backend_tests branch April 3, 2024 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add SQLite tests to CI?
2 participants