From: Thomas Huth <thuth@redhat.com>
To: Alberto Garcia <berto@igalia.com>, Kevin Wolf <kwolf@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH] iotests: Remove 030 from the auto group
Date: Thu, 24 Sep 2020 06:08:38 +0200 [thread overview]
Message-ID: <32238753-ca8c-82c2-7b4b-a92c9f2c21e8@redhat.com> (raw)
In-Reply-To: <w51ft789x1x.fsf@maestria.local.igalia.com>
On 23/09/2020 20.18, Alberto Garcia wrote:
> On Fri 04 Sep 2020 10:25:13 AM CEST, Kevin Wolf wrote:
>>> 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 <thuth@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.
>
> I also don't understand how this can fail... I assume the test is not
> running for that long in the cases when it fails, right?
Hard to say ... the problem only occurs occasionally, and I've never
seen it happen "live", only in the CI logs after the job has failed. I
guess you'd have to print timestamps in the code and then submit a lot
of jobs to the CI systems that are sensitive to this problem (e.g.
Cirrus and Travis) to find out...
Thomas
next prev parent reply other threads:[~2020-09-24 4:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 5:57 [PATCH] iotests: Remove 030 from the auto group Thomas Huth
2020-09-04 8:25 ` Kevin Wolf
2020-09-04 10:14 ` Thomas Huth
2020-09-04 10:37 ` Kevin Wolf
2020-09-04 10:38 ` Max Reitz
2020-09-04 11:51 ` Thomas Huth
2020-09-23 18:18 ` Alberto Garcia
2020-09-24 4:08 ` Thomas Huth [this message]
2020-09-04 8:31 ` Max Reitz
2020-09-04 8:31 ` Max Reitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32238753-ca8c-82c2-7b4b-a92c9f2c21e8@redhat.com \
--to=thuth@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).