From: Kevin Wolf <kwolf@redhat.com>
To: Thomas Huth <thuth@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: Fri, 4 Sep 2020 10:25:13 +0200 [thread overview]
Message-ID: <20200904082513.GA6237@linux.fritz.box> (raw)
In-Reply-To: <20200904055701.462482-1-thuth@redhat.com>
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 <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.
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
next prev parent reply other threads:[~2020-09-04 8:26 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 [this message]
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
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=20200904082513.GA6237@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).