Am 04.09.2020 um 07:57 hat Thomas Huth geschrieben: > Test 030 is still occasionally failing in the CI ... so for the > time being, let's disable it in the "auto" group. We can add it > back once it got more stable. > > Signed-off-by: Thomas Huth <th...@redhat.com>
I would rather just disable this one test function as 030 is a pretty important one that tends to catch bugs. > I just saw the problem here: > https://cirrus-ci.com/task/5449330930745344?command=main#L6482 > and Peter hit it a couple of weeks ago: > https://lists.gnu.org/archive/html/qemu-devel/2020-08/msg00136.html I wonder how this can still happen. The test should have more than enough time to complete now. Except if the throttling doesn't work as expected. I can't seem to reproduce this even if I add rather long delays. After 40 seconds, all jobs have moved either by 512k (which is STREAM_CHUNK) or not at all. What is interesting is that in both cases it's stream-node8, which is the job streaming from node6 to node8, and node8 is the top-level node. It's also the last job to be changed to full speed, so all others did succeed before. Kevin
