From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>, Thomas Huth <thuth@redhat.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: s390 private runner CI job timing out
Date: Thu, 6 Apr 2023 14:44:13 +0200 [thread overview]
Message-ID: <38857c4f-8a3f-909e-2517-4f094513ce99@linux.ibm.com> (raw)
In-Reply-To: <CAFEAcA_mUb+2gXDzMoD+rOvN9y5tvPyp4QXNtPGkk0bzg1t5vA@mail.gmail.com>
Am 06.04.23 um 14:39 schrieb Peter Maydell:
> On Thu, 6 Apr 2023 at 13:30, Thomas Huth <thuth@redhat.com> wrote:
>> The thing is: it shouldn't take that long to build QEMU and run the tests
>> here, theoretically. Some days ago, the job was finishing in 39 minutes:
>>
>> https://gitlab.com/qemu-project/qemu/-/jobs/3973481571
>>
>> The recent run took 74 minutes:
>>
>> https://gitlab.com/qemu-project/qemu/-/jobs/4066136770
>>
>> That's almost a factor of two! So there is definitely something strange
>> going on.
>
> So that 39 minute run was about 22 minutes compile, 17 minutes test.
> The 74 minute run was 45 minutes compile, 30 minutes test.
> The number of compile steps in meson was pretty much the same
> (10379 vs 10384) in each case. So the most plausible conclusion
> seems like "the VM mysteriously got slower by nearly a factor of 2",
> given that the slowdown seems to affect the compile and test
> stages about equally.
>
> The VM has been up for 44 days, so we can rule out "rebooted into
> a new kernel with some kind of perf bug".
I will ask around if we can get a higher share of the system.
next prev parent reply other threads:[~2023-04-06 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 15:15 s390 private runner CI job timing out Peter Maydell
2023-04-06 6:57 ` Thomas Huth
2023-04-06 9:21 ` Peter Maydell
2023-04-06 10:40 ` Christian Borntraeger
2023-04-06 10:44 ` Peter Maydell
2023-04-06 11:17 ` Christian Borntraeger
2023-04-06 12:05 ` Peter Maydell
2023-04-06 12:13 ` Christian Borntraeger
2023-04-06 12:28 ` Peter Maydell
2023-04-06 12:30 ` Thomas Huth
2023-04-06 12:39 ` Peter Maydell
2023-04-06 12:44 ` Christian Borntraeger [this message]
2023-04-06 14:18 ` Christian Borntraeger
2023-04-06 12:42 ` Christian Borntraeger
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=38857c4f-8a3f-909e-2517-4f094513ce99@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.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).