From: "Paul E. McKenney" <paulmck@kernel.org>
To: "Leonardo Brás" <leobras.c@gmail.com>
Cc: Akira Yokosawa <akiyks@gmail.com>, perfbook@vger.kernel.org
Subject: Re: [PATCH] utilities/gitlab-ci: Fully update system before building
Date: Fri, 4 Aug 2023 11:05:22 -0700 [thread overview]
Message-ID: <033be4b7-9403-4886-ab52-d704871d93ac@paulmck-laptop> (raw)
In-Reply-To: <d5e9d874f3c432e49c7c824160ced4cbd250f28e.camel@gmail.com>
On Fri, Aug 04, 2023 at 02:53:04PM -0300, Leonardo Brás wrote:
> On Fri, 2023-08-04 at 14:46 -0300, Leonardo Bras wrote:
> > Some recent CI errors come from the incompatibility between packages
> > pre-installed in the docker image and the ones installed via pacman.
> >
> > To avoid this, make a full system upgrade when installing the needed
> > packages.
> >
> > Signed-off-by: Leonardo Bras <leobras.c@gmail.com>
> > ---
> > utilities/gitlab-ci.yml | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/utilities/gitlab-ci.yml b/utilities/gitlab-ci.yml
> > index 544b9373..bcda8712 100644
> > --- a/utilities/gitlab-ci.yml
> > +++ b/utilities/gitlab-ci.yml
> > @@ -9,7 +9,7 @@ test_codesamples:
> > stage: test
> >
> > before_script:
> > - - pacman --noconfirm -Sy make gcc liburcu
> > + - pacman --noconfirm -Syu make gcc liburcu
> >
> > script:
> > - make -C CodeSamples/
> > @@ -19,7 +19,7 @@ generate_pdfs:
> > stage: build
> >
> > before_script:
> > - - pacman --noconfirm -Sy texlive-meta fig2dev ghostscript graphviz inkscape wget make which fontconfig git ttf-dejavu gnu-free-fonts ttf-liberation
> > + - pacman --noconfirm -Syu texlive-meta fig2dev ghostscript graphviz inkscape wget make which fontconfig git ttf-dejavu gnu-free-fonts ttf-liberation
> > - mkdir -p ~/.local/share/fonts && cp fonts/steel-city-comic.regular.ttf ~/.local/share/fonts/ && fc-cache
> >
> > script:
>
> Sorry about resending.
> I had an issue with credentials, please ignore the ones sent from my employer
> account: the gmail is the correct one.
Ah, I queued the wrong one. I updated it and pushed it out, could you
please double check?
Thanx, Paul
next prev parent reply other threads:[~2023-08-04 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 17:46 [PATCH] utilities/gitlab-ci: Fully update system before building Leonardo Bras
2023-08-04 17:53 ` Leonardo Brás
2023-08-04 18:05 ` Paul E. McKenney [this message]
2023-08-05 3:16 ` Leonardo Brás
2023-08-06 4:54 ` Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2023-08-04 17:50 Leonardo Bras
2023-08-04 17:41 Leonardo Bras
2023-08-04 17:54 ` Paul E. McKenney
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=033be4b7-9403-4886-ab52-d704871d93ac@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=leobras.c@gmail.com \
--cc=perfbook@vger.kernel.org \
/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).