[PATCH] CI: Use different containers for concurrent runner

[Simon Glass]

Hi Tom,

On Mon, 3 Feb 2025 at 10:14, Tom Rini <trini at konsulko.com> wrote:
>
> On Mon, Feb 03, 2025 at 09:25:54AM -0700, Simon Glass wrote:
>
> > When running multiple runners on the same machine, each should be in its
> > own container to avoid them interfering with either other.
> >
> > Add a container name for this. Ensure it is removed after use.
> >
> > Signed-off-by: Simon Glass <sjg at chromium.org>
> > ---
> >
> >  .gitlab-ci.yml | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> > index 1d4d3a85741..3487ad7e579 100644
> > --- a/.gitlab-ci.yml
> > +++ b/.gitlab-ci.yml
> > @@ -14,6 +14,10 @@ default:
> >  # in the u-boot tree at tools/docker/Dockerfile
> >  image: ${MIRROR_DOCKER}/trini/u-boot-gitlab-ci-runner:jammy-20240911.1-08Dec2024
> >
> > +services:
> > +  - name: container:${CI_JOB_ID}`
> > +    command: ["--rm"]
> > +
> >  # We run some tests in different order, to catch some failures quicker.
> >  stages:
> >    - testsuites
>
> This seems fine, but we should start by moving the image: line to be
> under the default: stanza, and then add this in default as well.

Actually it turns out that this doesn't work. See the failures at [1]

I was following the info at [2] but may need to ask on the forum. I
would expect separate filesystems for each container.

Regards,
Simon

[1] https://ci.u-boot.org/u-boot/u-boot/-/pipelines/343
[2] https://forum.gitlab.com/t/gitlab-runners-container-conflict-when-processing-more-than-1-job-at-the-same-time/86893/2