From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH] gitlab-ci.yml: Avoid recompiling the sources in the test jobs
Date: Tue, 26 Jan 2021 10:08:14 +0100 [thread overview]
Message-ID: <19cbfd81-3d33-dbc1-b8f4-fecdce8ce09c@redhat.com> (raw)
In-Reply-To: <ed621c17-43e4-3ae4-2a5f-56fb8d054e3f@redhat.com>
On 26/01/2021 08.36, Philippe Mathieu-Daudé wrote:
> On 1/26/21 7:57 AM, Thomas Huth wrote:
>> Currently, our check-system-* jobs are recompiling the whole sources
>> again. This happens due to the fact that the jobs are checking out
>> the whole source tree and required submodules again, and only try
>> to use the "build" directory with the binaries and object files as an
>> artifact from the previous stage - which simply does not work right
>> anymore (with the current version of meson). Due to some changed
>> time stamps, meson/ninja are always trying to rebuild the whole tree.
>>
>> In the long run, we could likely use "meson test --no-rebuild", but
>> there is still some work going on in that area to improve the user
>> experience. So until this has been done, simply avoid recompiling the
>> sources with a trick: pass NINJA=":" to the make process in the test
>> jobs. Also check out the submodules manually before updating the
>> timestamps in the build folder, so that the binaries are definitely
>> newer that all the source files.
>> This saves ca. 10 - 15 minutes of precious CI cycles in each run.
>>
>> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> .gitlab-ci.yml | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>> index de3a3d25b5..16fea25ba9 100644
>> --- a/.gitlab-ci.yml
>> +++ b/.gitlab-ci.yml
>> @@ -38,9 +38,11 @@ include:
>> stage: test
>> image: $CI_REGISTRY_IMAGE/qemu/$IMAGE:latest
>> script:
>> + - scripts/git-submodule.sh update
>> + $(grep GIT_SUBMODULES build/config-host.mak | sed 's/GIT_SUBMODULES=//')
>> - cd build
>> - find . -type f -exec touch {} +
>> - - make $MAKE_CHECK_ARGS
>> + - make NINJA=":" $MAKE_CHECK_ARGS
>
> This ninja trick deserves a comment in the YAML file.
I'll add:
# Avoid recompiling by hiding ninja with NINJA=":"
Ok?
Thomas
next prev parent reply other threads:[~2021-01-26 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 6:57 [PATCH] gitlab-ci.yml: Avoid recompiling the sources in the test jobs Thomas Huth
2021-01-26 7:36 ` Philippe Mathieu-Daudé
2021-01-26 9:08 ` Thomas Huth [this message]
2021-01-26 9:38 ` Philippe Mathieu-Daudé
2021-01-26 13:36 ` Wainer dos Santos Moschetta
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=19cbfd81-3d33-dbc1-b8f4-fecdce8ce09c@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).