Skip to content

tests/verity-forking: Limit execution time to 10s #163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 28, 2025

Conversation

cgwalters
Copy link
Collaborator

This test was running over 60s on my machine (32 cores); digging in it's because the raw variant was simply not getting anywhere close to hitting 100 successes.

First, rework to use a JoinSet instead of a tokio::join! so we see the completions as they come in instead of waiting for all of them.

Add a hard limit of execution time of 10s.

Add an assertion that the copy variant succeeds at least once. For the other two, we can't really make any assertions at all.

This test was running over 60s on my machine (32 cores); digging
in it's because the raw variant was simply not getting anywhere
close to hitting 100 successes.

First, rework to use a JoinSet instead of a tokio::join! so
we see the completions as they come in instead of waiting for
all of them.

Add a hard limit of execution time of 10s.

Add an assertion that the *copy* variant succeeds at least once.
For the other two, we can't really make any assertions at all.

Signed-off-by: Colin Walters <[email protected]>
@cgwalters cgwalters requested a review from Johan-Liebert1 July 25, 2025 12:06
@Johan-Liebert1
Copy link
Collaborator

LGTM

@Johan-Liebert1 Johan-Liebert1 merged commit c74efd0 into containers:main Jul 28, 2025
14 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants