workflow: run pytests via matrix to get more parallel runs #910
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.
This commit moves the test running into a matrix so that
we get more parallel testing. It will still be (much) dominated
by
test_build_disk.py
but at least this way a flaky test ine.g.
test_container
is much faster to re-run.With multiple VMs we can probably also parallelize the tests [1]
because we have less images per VM to test so diskspace
may be less of an issue.
test: split test_build.py into test_build_{disk,iso}
Split this big test into smaller files because we
will run the tests in parallel via a dynamic (per-file)
github matrix. This will allow faster tests and easier
re-runs if a single test is flaky only a small subset
will have to be retriggered.
[1] #787