You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We bolted on kola testiso into kola a while ago to get coverage for our bare metal install workflows, but there are a lot of nice features in kola 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 other kola tests that run for a given build.
The text was updated successfully, but these errors were encountered:
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 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: