Fix: Make Test Suite Parallelizable #1273
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fpjentzsch
changed the title
|
I also made the notebook tests and end2end tests parallelizable while keeping dependent tests grouped together using the For bnn_pynq, different scenarios ( |
fpjentzsch
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the FINN+ CI we want to speed up the test suite.
Previously, the test suite was parallelizable only with the pytest-xdist
--dist loadfilescheduler, because some tests assume all tests within the same file are run in-order or at least not in parallel.This refactors the offending tests that I found (except end2end tests for now, which really depend on each other) so that we can use a better scheduler (
--dist worksteal) for most of the test suite.