Closed jelly closed 3 months ago
This failure is related. Not sure if it's a missed spot or the patch here needs to try/wait harder?
And it goes red of course. The screenshot clearly shows that not all memory was allocated yet.
I could change this to wait on memory to be 300, that would be better, because CPU usage is not a real indicator anyway. or alternatively wait for a smaller cpu usage, locally it is 0%
. Lowered it to < 10
, lets see now it might need a longer timeout...
There is one failure left, where it flakes in a different way. I'd say this is progress :)
This failure is also something else.
Played around in this PR https://github.com/cockpit-project/cockpit-podman/pull/1771