From: "Alex Bennée" <alex.bennee@linaro.org>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: "Beraldo Leal" <bleal@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Thomas Huth" <thuth@redhat.com>,
"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: Thu, 18 Aug 2022 08:07:00 +0100 [thread overview]
Message-ID: <87zgg2rpu5.fsf@linaro.org> (raw)
In-Reply-To: <20220817034630.1600434-1-bmeng.cn@gmail.com>
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?
>
> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
> ---
>
> .gitlab-ci.d/buildtest.yml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index 1931b77b49..52d45508fb 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -495,6 +495,7 @@ check-gprof-gcov:
> variables:
> IMAGE: ubuntu2004
> MAKE_CHECK_ARGS: check
> + timeout: 90m
> after_script:
> - ${CI_PROJECT_DIR}/scripts/ci/coverage-summary.sh
--
Alex Bennée
next prev parent reply other threads:[~2022-08-18 7:11 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 [this message]
2022-08-18 7:25 ` Thomas Huth
2022-08-19 10:23 ` Alex Bennée
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=87zgg2rpu5.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.