All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Bin Meng" <bmeng.cn@gmail.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] .gitlab-ci.d/buildtest.yml: Increase the check-gprof-gcov job timeout
Date: Fri, 19 Aug 2022 11:23:57 +0100	[thread overview]
Message-ID: <874jy84jkn.fsf@linaro.org> (raw)
In-Reply-To: <8c005cf6-24c0-bdbc-e892-3a4c520bb0ad@redhat.com>


Thomas Huth <thuth@redhat.com> writes:

> On 18/08/2022 09.07, Alex Bennée wrote:
>> Bin Meng <bmeng.cn@gmail.com> writes:
>> 
>>> Current project timeout is 1 hour, but the check-gprof-gcov job never
>>> completes within 1 hour. Increase the job timeout to 90 minutes.
>> I've tried to do some data mining on this test which seems to
>> indicate
>> that the average successful completion time for gprof-gcov is 27 mins.
>> So it seems the sometimes *something* causes it to run a lot more
>> slowly. I wonder if increasing the timeout just masks the problem?
>
> I think it's very certainly the migration test that is causing the
> timeout now. In former times, the test was skipped, see e.g.:
>
>  https://gitlab.com/qemu-project/qemu/-/jobs/2795092179#L48
>
> Since commit 2649a72555e the tests are run and take ca. 2 * 20 minutes:
>
>  https://gitlab.com/qemu-project/qemu/-/jobs/2798625330#L48
>
> That's why I started a discussion here for how to reduce the amount of
> time of the migration tests in the CI:
>
>  https://lists.gnu.org/archive/html/qemu-devel/2022-08/msg01219.html

OK I have queued to this patch to testing/next while the discussion is
had. I'll update the commit message.

-- 
Alex Bennée


      reply	other threads:[~2022-08-19 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17  3:46 [PATCH] .gitlab-ci.d/buildtest.yml: Increase the check-gprof-gcov job timeout Bin Meng
2022-08-17 14:43 ` Thomas Huth
2022-08-18  7:07 ` Alex Bennée
2022-08-18  7:25   ` Thomas Huth
2022-08-19 10:23     ` Alex Bennée [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=874jy84jkn.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=bmeng.cn@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.