From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: "Willian Rampazzo" <willianr@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P . Berrange" <berrange@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH 6/9] gitlab-ci: Split gprof-gcov job
Date: Thu, 27 May 2021 08:03:51 +0200 [thread overview]
Message-ID: <177aee51-ac23-5321-021c-a8244ddf254e@redhat.com> (raw)
In-Reply-To: <8c74e90e-ed4c-9e96-cf87-c0c413e48eaa@amsat.org>
On 25/05/2021 12.21, Philippe Mathieu-Daudé wrote:
> On 5/25/21 10:25 AM, Philippe Mathieu-Daudé wrote:
>> This job is hitting the 70min limit, so split it in 2 tasks.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> ---
>> .gitlab-ci.d/buildtest.yml | 17 ++++++++++++++---
>> 1 file changed, 14 insertions(+), 3 deletions(-)
>>
>> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
>> index f903fdea3f4..894732e203d 100644
>> --- a/.gitlab-ci.d/buildtest.yml
>> +++ b/.gitlab-ci.d/buildtest.yml
>> @@ -564,16 +564,27 @@ check-deprecated:
>> allow_failure: true
>>
>> # gprof/gcov are GCC features
>> -gprof-gcov:
>> +build-gprof-gcov:
>> extends: .native_build_job_template
>> needs:
>> job: amd64-ubuntu2004-container
>> variables:
>> IMAGE: ubuntu2004
>> CONFIGURE_ARGS: --enable-gprof --enable-gcov
>> - MAKE_CHECK_ARGS: check
>> TARGETS: aarch64-softmmu ppc64-softmmu s390x-softmmu x86_64-softmmu
>> - timeout: 70m
>> + artifacts:
>> + expire_in: 1 days
>> + paths:
>> + - build
>
> FYI this job takes 28min:
> https://gitlab.com/philmd/qemu/-/jobs/1290778672
>
>> +
>> +check-gprof-gcov:
>> + extends: .native_test_job_template
>> + needs:
>> + - job: build-gprof-gcov
>> + artifacts: true
>> + variables:
>> + IMAGE: ubuntu2004
>> + MAKE_CHECK_ARGS: check
>> after_script:
>> - ${CI_PROJECT_DIR}/scripts/ci/coverage-summary.sh
>
> and this one 23min:
> https://gitlab.com/philmd/qemu/-/jobs/1290778751
So why are they taking less than 70 minutes when split in two parts, but are
exceeding the 70 minutes when done in one job?
That does not make sense...
Thomas
next prev parent reply other threads:[~2021-05-27 6:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 8:25 [PATCH 0/9] gitlab-ci: Make mainstream CI green again Philippe Mathieu-Daudé
2021-05-25 8:25 ` [PATCH 1/9] gitlab-ci: Extract all default build/test jobs to buildtest.yml Philippe Mathieu-Daudé
2021-05-25 11:05 ` Alex Bennée
2021-05-25 8:25 ` [PATCH 2/9] gitlab-ci: Move current job set to qemu-project.yml Philippe Mathieu-Daudé
2021-05-25 11:05 ` Alex Bennée
2021-05-25 8:25 ` [PATCH 3/9] gitlab-ci: Document how forks can use different set of jobs Philippe Mathieu-Daudé
2021-05-25 11:06 ` Alex Bennée
2021-05-25 14:30 ` Willian Rampazzo
2021-05-25 8:25 ` [PATCH 4/9] gitlab-ci: Extract cross-container jobs to container-cross.yml Philippe Mathieu-Daudé
2021-05-25 11:06 ` Alex Bennée
2021-05-25 14:32 ` Willian Rampazzo
2021-05-25 8:25 ` [PATCH 5/9] gitlab-ci: explicitly reference the upstream registry Philippe Mathieu-Daudé
2021-05-25 11:10 ` Alex Bennée
2021-05-25 11:39 ` Philippe Mathieu-Daudé
2021-05-25 8:25 ` [PATCH 6/9] gitlab-ci: Split gprof-gcov job Philippe Mathieu-Daudé
2021-05-25 10:21 ` Philippe Mathieu-Daudé
2021-05-27 6:03 ` Thomas Huth [this message]
2021-05-27 13:04 ` Alex Bennée
2021-05-25 14:34 ` Willian Rampazzo
2021-06-07 11:36 ` Alex Bennée
2021-05-25 8:25 ` [PATCH 7/9] gitlab-ci: Keep Avocado reports during 1 week Philippe Mathieu-Daudé
2021-05-25 11:11 ` Alex Bennée
2021-05-25 14:35 ` Willian Rampazzo
2021-05-25 8:25 ` [PATCH 8/9] gitlab-ci: Run Avocado tests manually (except mainstream CI) Philippe Mathieu-Daudé
2021-05-25 11:25 ` Alex Bennée
2021-05-27 6:08 ` Thomas Huth
2021-05-25 8:25 ` [PATCH 9/9] gitlab-ci: Use absolute path and simplify firmware jobs Philippe Mathieu-Daudé
2021-05-25 8:56 ` Daniel P. Berrangé
2021-05-25 9:02 ` Philippe Mathieu-Daudé
2021-05-27 16:04 ` [PATCH 0/9] gitlab-ci: Make mainstream CI green again Philippe Mathieu-Daudé
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=177aee51-ac23-5321-021c-a8244ddf254e@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
--cc=willianr@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).