-
Notifications
You must be signed in to change notification settings - Fork 631
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
Improved test execution #2482
Improved test execution #2482
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #2482 +/- ##
==========================================
- Coverage 84.81% 83.90% -0.91%
==========================================
Files 330 224 -106
Lines 39474 24374 -15100
==========================================
- Hits 33481 20452 -13029
+ Misses 5993 3922 -2071
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
199a14d
to
efbb7b9
Compare
233c26d
to
4f5b50a
Compare
b800333
to
c4b8bff
Compare
- Introduced flaky test marker - Fixed failing tests - Disable locks in tests - Disabled tqdm.interval-monitor in tests - Improved test github action - Introduced caching around posixpath.relpath() as it caused a surprising slowdown in tests - Ensure `test_dataset` is always in a consistent location - Moved some tests to use local datastore vs. hub-cloud
eea5817
to
6faa6ff
Compare
# Conflicts: # deeplake/core/seed.py
Kudos, SonarCloud Quality Gate passed! |
# Conflicts: # deeplake/core/vectorstore/test_deeplake_vectorstore.py # deeplake/enterprise/test_pytorch.py
🚀 🚀 Pull Request
Changes
Making tests pass consistently and easier to troubleshoot when they don't.
pytest.mark.slow
to make it easier to run the full suite consistently by skipping the slow tests. The fast tests run first on the build system for quicker feedback on failurespytest.mark.flaky
and moved them to a separate build stepI didn't do a lot with the overall code performance, but I addressed these two issues:
test_dataset
to be recreated/re-downloaded in several locations, so I made it always be created in the repo rootThere was also a couple previously-failing (and maybe newly failing?) tests I fixed.
Other PRs that go along with this: