On 8/24/25 4:03 PM, Mark Wielaard wrote:
Hi Jeff,
On Sun, Aug 24, 2025 at 08:07:32AM -0600, Jeff Law wrote:
On 8/24/25 6:39 AM, Mark Wielaard wrote:
If the port has a (qemu) emulator we could create a x86_64 container
for it and run it once a month/week on one of the faster
builder.sourceware.org workers.
That's what my tester does for alpha, m68k, hppa, sh4, ppc, s390.
Bootstrap, regression test, build glibc & kernel.
Is there a writeup of how this is setup? Would it make sense to try to
replicate this in the public buildbot x86_64 container environment?
It's actually quite simple. You just need a suitably complete root
filesystem. Convert that into a docker container that you can spin up
at will. Mine started their life as either official containers from
debian or a debootstrap RFS imported into docker as an image. apt-get
to add whatever packages are needed to bootstrap gcc and away we go.
You need some kind of way to connect the running container to jenkins.
In my case I use the jenkins docker swarm plugin which will spin up my
container which connects the container to the server via jnlp. It's the
weak link in the system IMHO due to the lack of maintenance on the
jenkins plugin. But it was probably still more sensible to stand up and
maintain than K8.
Bootstrapping and regression testing something like alpha, m68k, hppa,
whatever take ~24hrs on a 40c skylake. So those fire once a week. The
more traditional crosses take an hour or so, so those spin up daily.
Or do you like help making your tester more public?
All the scripts that drive it are on github. The docker containers are
trivial to make available as well.
Jeff
