Hi,
> Is there anything else that needs to be done?
No there isn't, it was working properly when it was first rolled out. I've
started seen this issue today and looks like it only affecting some runners, so
I am guessing something got updated or new runners where added. Bart is on
vacation
On Mon, Feb 24, 2020 at 11:08 am, Michael Catanzaro
wrote:
I have two failed builds on flatpak-gcc176 (also broken) and two
failed builds on flatpak-gcc150.fsffrance.org (also broken). My plan
is to keep retrying until I get flatpak-progress again. I need a
successful build urgently because
On Mon, Feb 24, 2020 at 4:48 pm, Bastien Nocera
wrote:
Ran it 3 separate times, on 3 different runners, to no avail.
I'm struggling with this currently.
From yesterday:
https://gitlab.gnome.org/GNOME/epiphany/pipelines/10/builds
I have a failed build on flatpak-gcc175 (broken), then a
On Mon, 2020-02-24 at 08:19 -0600, Michael Catanzaro wrote:
> On Mon, Feb 24, 2020 at 10:11 am, Bastien Nocera
> wrote:
> > It uses the flatpak_ci_initiative.yml template and throws this
> > error:
> > bwrap: Creating new namespace failed, likely because the kernel
> > does
> > not support user
On Mon, Feb 24, 2020 at 10:11 am, Bastien Nocera
wrote:
It uses the flatpak_ci_initiative.yml template and throws this error:
bwrap: Creating new namespace failed, likely because the kernel does
not support user namespaces. bwrap must be installed setuid on such
systems.
I'm seeing this
On Wed, 2020-02-19 at 14:50 +0100, Bartłomiej Piotrowski wrote:
> Hello,
>
> For historical reasons™ all GitLab runners were running with
> privileged
> mode enabled. The happy side effect of this fact is that nothing
> special
> was ever needed to run Docker or flatpak builds. It also means we
>
