integration/container: Deflake TestWaitBlocked and TestWaitRestartedContainer#49618
integration/container: Deflake TestWaitBlocked and TestWaitRestartedContainer#49618vvoland merged 2 commits intomoby:masterfrom
Conversation
ba8bb31 to
3cca323
Compare
4e4a511 to
876007c
Compare
|
Does the |
876007c to
16d7d8a
Compare
|
Nope, the 10s timeout is hit on the daemon side so it's not about the 2s wait timeout. I don't have a good explanation yet why removing Parallel works. Or maybe it actually doesn't and I wasn't able to hit the jackpot 🙈 I'm still willing to investigate this more, but would like to first make sure that removing Parallel is the key here. |
|
Actually, let me try to test one more change on this one. |
16d7d8a to
a39d6c9
Compare
…tainer Signed-off-by: Paweł Gronowski <[email protected]>
It seems to help with the flakiness in the CI. However, I can't reproduce the flakiness locally. Signed-off-by: Paweł Gronowski <[email protected]>
a39d6c9 to
ac34bd9
Compare
|
I can't reproduce the flakiness locally so I think it's related to the system load of the CI machine? 🤷🏻 |
|
Reverted to the initial approach |
robmry
left a comment
There was a problem hiding this comment.
Thank you for investigating ... is the conclusion that parallel stops actually are flaky in the daemon, so it's not "just" a test problem? (Do we need an issue to track that?)
Either way, we can't have flaky tests - so this change LGTM.
|
No concrete idea yet, for some reason the container just doesn't exit after the daemon sends the SIGTERM. I'll open a ticket for it and keep an eye on this test. |
Remove Parallel execution and increase stop timeout seems to help.