public inbox for
 help / color / mirror / Atom feed
From: Christophe Lyon <>
Cc: Luis Machado <>,
	Szabolcs Nagy <>
Subject: Arm GDB buildbot workers
Date: Thu, 7 Jul 2022 15:50:51 +0200	[thread overview]
Message-ID: <> (raw)


As discussed on IRC we are going to enable workers on our Ampere "big"

For a start, we are going to try with GDB, having 4 different docker
containers on the machine covering ubuntu-20.04/ubuntu-22.04 x
arm64/armhf, using 4 CPUs each.

I am not sure if we need a single password for all workers, or 4 of them?

For each of them that means:

Once these work, I'll add more containers for glibc, binutils and
hopefully GCC.

I think this small patch is desirable:
diff --git a/builder/containers/ b/builder/containers/
index 31cdbc9..220e82e 100755
--- a/builder/containers/
+++ b/builder/containers/
@@ -18,6 +18,7 @@ fi

  # Fill in the info visible in the buildbot website
  # objcopy gives us the binutils version, iconv the glibc version
+mkdir -p $worker_dir/info
  echo > $worker_dir/info/admin
  echo $IMAGE_NAME > $worker_dir/info/host
  gcc --version | head -1 >> $worker_dir/info/host

Let me know if I missed something.


IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

             reply	other threads:[~2022-07-07 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 13:50 Christophe Lyon [this message]
2022-07-07 23:13 ` Mark Wielaard
2022-07-08 10:11   ` Christophe Lyon
2022-07-08 10:46     ` Mark Wielaard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).