Skip to content

kolaTestIso: retry failed tests #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 2 commits into from
Mar 27, 2025
Merged

Conversation

dustymabe
Copy link
Member

We've been seeing a lot of testiso flakes lately. Let's try to give ourselves a break by retrying like we do for normal kola runs.

This is slightly different because it's not done inside kola but outside kola. For the inside kola retry of testiso we'll wait for coreos/coreos-assembler#3989 to happen.

We've been seeing a lot of testiso flakes lately. Let's try to give
ourselves a break by retrying like we do for normal kola runs.

This is slightly different because it's not done inside kola but
outside kola. For the inside kola retry of testiso we'll wait for
coreos/coreos-assembler#3989 to happen.
@dustymabe dustymabe force-pushed the dusty-retry-testiso branch from 434451e to 74be4a6 Compare March 23, 2025 17:58
@dustymabe
Copy link
Member Author

dustymabe commented Mar 26, 2025

So for the life of me I don't understand it but there hasn't been a testiso failure (and thus falling through to hit this retry code) once since I switched the pipeline over to use my branch (to test this).

Thoughts on just merging it (so we can switch the pipeline back to not using my fork) and then if it really is broken we'll PR a fixup?

@marmijo
Copy link
Member

marmijo commented Mar 26, 2025

That works for me. It's either that or switch the pipeline back now to see if the tests start failing again. I'm all for merging this now though.

Copy link
Member

@marmijo marmijo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@aaradhak aaradhak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for merging this, we can work on a fix if this is throwing an issue.

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.

3 participants