mirror of
https://github.com/optim-enterprises-bv/kubernetes.git
synced 2025-12-15 20:37:39 +00:00
There is a test in wait.sh integration suite which is checking the given timeout value(passed by user) is equal to actual happened timeout value. However, this test rarely gets `no matching resources found` error and causes flakyiness. The reason is we are running wait command, immediately after applying deployment. In reality, timeout test does not care about deployment, since it is testing the timeout by passing invalid configurations. But we need this deployment to not get `no matching resources found` error. That's why, this PR adds deployment assertion before executing wait command.
3.0 KiB
3.0 KiB