reverts removal of parallel run from critest

Signed-off-by: Paul S. Schweigert <paulschw@us.ibm.com> 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.
psschwei · May 12, 2022 · bdc6cca · bdc6cca
1 parent 9aa6725
commit bdc6cca
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/Vagrantfile b/Vagrantfile
@@ -271,8 +271,7 @@ EOF
         fi
         trap cleanup EXIT
         ctr version
-        # TODO run in parallel, see https://github.com/containerd/containerd/issues/6903
-        critest --ginkgo.skip='HostIpc is true' --report-dir="${REPORT_DIR}"
+        critest --parallel=$[$(nproc)+2] --ginkgo.skip='HostIpc is true' --report-dir="${REPORT_DIR}"
     SHELL
   end
 

diff --git a/script/setup/critools-version b/script/setup/critools-version
@@ -1 +1 @@
-v1.24.0
+v1.24.1