[release/1.6] Reverts removal of parallel run from critest#6942
[release/1.6] Reverts removal of parallel run from critest#6942fuweid merged 1 commit intocontainerd:release/1.6from
Conversation
|
Hi @psschwei. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/ok-to-test |
|
I'll reset it again but this was an interesting error in vagrant on building the containerd binary: nvm fixed here: #6941 :-) |
|
@psschwei needs rebase on top of phil's pr ^ when that is merged.. |
Signed-off-by: Paul S. Schweigert <[email protected]> (cherry picked from commit 7300296) As discussed in containerd#6903, running ginkgo tests in parallel while trying to skip wasn't working. However, now that kubernetes-sigs/cri-tools#930 has fixed the issue upstream, we can revert back to running our tests in parallel with the skip. Signed-off-by: Paul S. Schweigert <[email protected]>
Signed-off-by: Paul S. Schweigert [email protected]
(cherry picked from commit 7300296)
As discussed in #6903,
running ginkgo tests in parallel while trying to skip wasn't working.
However, now that
kubernetes-sigs/cri-tools#930 has fixed the
issue upstream, we can revert back to running our tests in parallel
with the skip.
Cherry pick of #6938
Signed-off-by: Paul S. Schweigert [email protected]