[test/DNM] ci: run the cri-o suite with bats --timing - #683
Draft
kolyshkin wants to merge 1 commit into
Draft
Conversation
Not for merge. Cuts the matrix down to the one job that takes 40 minutes (stable, critest=0), drops the conmon job, and patches cri-o's test_runner.sh to pass --timing, so that the TAP output carries a duration per test instead of having to be reconstructed from the timestamps of buffered output. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
kolyshkin
force-pushed
the
dnm-crio-timing
branch
from
August 19, 2026 10:41
b0fa342 to
4614818
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Not for merge -- a measurement run.
The cri-o
critest=0job takes about 40 minutes and we would like to know where they go. Its TAP output is buffered (ordered output with--jobs), so wall-clock timestamps only tell us when a result was printed, not how long the test took: in a recent run 334 results were flushed in the same microsecond, after a 28 minute silence held by a single test.So: cut the matrix to that one job, drop the conmon job, and patch cri-o's
test_runner.shto runbats --timing, which puts a duration on every TAP line.Results will be used to decide which test files are worth skipping in this repo's CI (it already skips
seccomp*,image,policyandcrio-wipe), and to look into the one test that appears to take half an hour on its own.