Hi Michael,
On 7/11/23 10:49, Michael S. Tsirkin wrote:
so we keep making timeouts longer for CI but one has to stop
somewhere. netdev socket test recently failed for me again
even though it's at 2 minutes already.
here's an experiment for netdev-socket.
if this works well for a while we can generalize to other
tests.
Michael S. Tsirkin (2):
osdep: add getloadavg
netdev: set timeout depending on loadavg
The 2 problems I see with this approach are:
- Machine load can vary *after* the test is started,
- Test environment isn't really reproducible.
Are those netdev tests only failing due to high load?
Maybe we need to disable them on CI and run them manually...
Regards,
Phil.
