public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org
Subject: Re: [RFC,PATCH] containers: extract bb-start.sh to a file and reuse it
Date: Sat, 18 Jun 2022 20:35:06 +0200	[thread overview]
Message-ID: <90c38f7f-0244-fc5d-85a5-8adab72023a9@suse.cz> (raw)
In-Reply-To: <Yq3zfXYwSVnXO585@wildebeest.org>

On 6/18/22 17:47, Mark Wielaard wrote:
> Hi Martin,
> 
> On Fri, Jun 17, 2022 at 11:17:28AM +0200, Martin Liška wrote:
>> Doing echo "..." > bb-start.sh adds one more level of escaping
>> and it is quite ugly. Use rather a proper file and discard all
>> the Debian switch to bash and back.
>>
>> Mark can you please test it if it works with the newly set 2 ENV variables:
>> ENV IMAGE_NAME=debian-stable
>> ENV CCACHE_LIBDIR=/usr/lib/ccache
> 
> I like this. But we cannot simply COPY in the bb-start.sh file.
> Because it isn't available on the container host. The
> DockerLatentWorker only sents the Container file. But we could fetch
> it from the git repo using:
> 
> RUN wget -O /home/builder/bb-start.sh \
>     'https://sourceware.org/git/?p=builder.git;a=blob_plain;f=builder/containers/bb-start.sh' \
>     && chmod 755 /home/builder/bb-start.sh

Good, I've done that and pushed to main.

However, I see an error now:
https://builder.sourceware.org/buildbot/#/builders/97/builds/248

Can you please check buildbot master log files in order to investigate what's wrong?

Thanks,
Martin

> 
> We could also git clone the whole builder.git repo and then copy the
> bb-start.sh file from the checkout, but this seems simpler.
> 
> If this works for you, please commit.
> 
> Thanks,
> 
> Mark


  reply	other threads:[~2022-06-18 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  9:17 Martin Liška
2022-06-18 15:47 ` Mark Wielaard
2022-06-18 18:35   ` Martin Liška [this message]
2022-06-18 18:38     ` Martin Liška
2022-06-18 20:11     ` Mark Wielaard
2022-06-19  7:12       ` Martin Liška

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=90c38f7f-0244-fc5d-85a5-8adab72023a9@suse.cz \
    --to=mliska@suse.cz \
    --cc=buildbot@sourceware.org \
    --cc=mark@klomp.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 read-only IMAP folder(s) and NNTP newsgroup(s).