From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, Peter Maydell <peter.maydell@linaro.org>
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:42:24 +0200 [thread overview]
Message-ID: <f8765cb0-1faf-9848-1d33-3d8fc348fa63@linux.ibm.com> (raw)
In-Reply-To: <2e529c06-199f-6d5a-a75b-5b88aae44b2c@redhat.com>
Am 06.04.23 um 14:30 schrieb Thomas Huth:
> On 06/04/2023 14.13, Christian Borntraeger wrote:
>>
>>
>> Am 06.04.23 um 14:05 schrieb Peter Maydell:
>>> On Thu, 6 Apr 2023 at 12:17, Christian Borntraeger
>>> <borntraeger@linux.ibm.com> wrote:
>>>>
>>>> Am 06.04.23 um 12:44 schrieb Peter Maydell:
>>>>> On Thu, 6 Apr 2023 at 11:40, Christian Borntraeger
>>>>> <borntraeger@linux.ibm.com> wrote:
>>>>>> Am 06.04.23 um 11:21 schrieb Peter Maydell:
>>>>>>> Christian, does our S390X machine get a guaranteed amount of CPU,
>>>>>>> or does it depend on what else is running on the hardware?
>>>>>>
>>>>>> I think its a shared system with shared CPUs. Can you check the steal
>>>>>> time in top or proc? If this is far too high we could ask to give you
>>>>>> more weight for that VM.
>>>>>
>>>>> It's idle at the moment and steal time seems to be low (0.0 .. 0.3);
>>>>> I'll try to remember to check next time it's running a job.
>>>>>
>>>>
>>>> Do you have /proc/stat ?
>>>
>>> Yes; hopefully it means more to you than it does to me :-)
>>>
>>> linux1@qemu01:~$ cat /proc/stat
>>> cpu 60904459 604975 15052194 1435958176 17128179 351949 758578 22218760 0 0
>>> cpu0 15022535 146734 3786909 358774818 4283172 98313 237156 5894809 0 0
>>> cpu1 15306890 151164 3746024 358968957 4378864 85629 172492 5434255 0 0
>>> cpu2 15307709 157180 3762691 359141276 4138714 85736 176367 5474594 0 0
>>> cpu3 15267324 149895 3756569 359073124 4327428 82269 172562 5415101 0 0
>>
>> This is
>> user,nice,system,idle,iowait,irq,softirq,steal,guest,guest_nice
>> So overall there is some (20-30% since the last reboot) steal going on.
>> Not sure if this is the real problem since it is only Ubuntu 20.04.
>> Does a higher timeout make the problem go away?
>
> 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.
But this has 786 instead of 659 tests, no?
prev parent reply other threads:[~2023-04-06 12:43 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
2023-04-06 14:18 ` Christian Borntraeger
2023-04-06 12:42 ` Christian Borntraeger [this message]
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=f8765cb0-1faf-9848-1d33-3d8fc348fa63@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).