Retry buildkite isolated tests since they are known to be flaky

Passed in 29m 12s
:pipeline:[[ -f ".buildkite/pipeline.yml" ]] && buildkite-agent pipeline upload --replace || true
Waited 1s
·
Ran in 20s
:docker: Buildmake test-images && docker run --rm -v /local/home/buildkite-agent/builds/ip-10-0-0-182-36/firecracker-microvm/firecracker-containerd:/mnt debian:bullseye-slim rm -rf /mnt/tools/image-builder/rootfs && sudo install -d -o root -g buildkite-agent -m 775 "/local/artifacts/4250" && cp tools/image-builder/rootfs.img "/local/artifacts/4250/"
Waited 1s
·
Ran in 9m 23s
:lint-roller: loop device cleanupsudo losetup -l
Waited 1s
·
Ran in 15s
:protractor: verify protomake proto && test -z "$(git status --porcelain)" && exit 0 || git status && echo -e '\nGenerated protobuf code differs from committed, please run "make proto" and commit the updated files.\n' && exit 1
Waited 1s
·
Ran in 36s
⚙️ unit testscp "/local/artifacts/4250/rootfs.img" tools/image-builder/rootfs.img && make test-in-docker
Waited 1s
·
Ran in 1m 37s
🏃 runtime isolated testsmake -C runtime integ-test FICD_DM_POOL=build_4250_runtime
Waited 1s
·
Ran in 19m 40s
🏋️ stress testsmake -C runtime integ-test-TestMultipleVMs_Isolated FICD_DM_POOL=stress4250
Waited 1s
·
Ran in 3m 7s
🚨 example testsmake -C examples integ-test TEST_POOL=build_4250_example
Waited 1s
·
Ran in 55s
🚨 cri conformance testsmake -C runtime critest FICD_DM_POOL=build_4250_critest
Waited 1s
·
Ran in 4m 22s
Total Job Run Time: 40m 15s