-
Notifications
You must be signed in to change notification settings - Fork 170
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
fold kola testiso
into kola run
#3989
Comments
If no one else is looking at this, I'd like to give it a go. That's actually something I was considering during my work on some of the kola testiso tests. |
Already had talked to @nikita-dubrovskii on this one so it's scheduled for him for next sprint. It would be good to have more people involved in design and code review, though, so you two can maybe have some sessions up front discuss the strategy once you're familiar with the code. Feel free to add me. |
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.
We bolted on
kola testiso
intokola
a while ago to get coverage for our bare metal install workflows, but there are a lot of nice features inkola run
that haven't been extended there and wouldn't really make sense to duplicate (for example here is a case where we duplicated a feature, but wouldn't have had to).Let's make an effort to fold our testiso tests back into
kola run
and they can be ran in parallel and scheduled along with all the otherkola
tests that run for a given build.The text was updated successfully, but these errors were encountered: