diff mbox series

[06/12] CI: Mark Archlinux/x86 as allowing failures

Message ID 20240711111517.3064810-7-andrew.cooper3@citrix.com (mailing list archive)
State New
Headers show
Series CI: part 3 (slimline, and PPC/RISCV fixes) | expand

Commit Message

Andrew Cooper July 11, 2024, 11:15 a.m. UTC
Archlinux is a rolling distro, and is subject to arbitrary changes as the
container is rebuilt.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
---
CC: Anthony PERARD <anthony.perard@vates.tech>
CC: Juergen Gross <jgross@suse.com>
CC: Roger Pau Monné <roger.pau@citrix.com>
CC: Jan Beulich <JBeulich@suse.com>
CC: Stefano Stabellini <sstabellini@kernel.org>
CC: Julien Grall <julien@xen.org>
CC: Oleksii Kurochko <oleksii.kurochko@gmail.com>
CC: Shawn Anastasio <sanastasio@raptorengineering.com>
---
 automation/gitlab-ci/build.yaml | 2 ++
 1 file changed, 2 insertions(+)

Comments

Anthony PERARD July 11, 2024, 1:37 p.m. UTC | #1
On Thu, Jul 11, 2024 at 12:15:11PM +0100, Andrew Cooper wrote:
> Archlinux is a rolling distro, and is subject to arbitrary changes as the
> container is rebuilt.

I disagree about the changes been arbitrary, it is just new version of
software. :-)

But I guess "arbirary changes" could be a description for package been
removed from the main/official archive, and left for the users to build
themselfs.

> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>

Anyway:
Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>

(Next, automatically rebuild the container every month, I could probably
revive my old patch series doing that)

Cheers,
Andrew Cooper July 11, 2024, 3:24 p.m. UTC | #2
On 11/07/2024 2:37 pm, Anthony PERARD wrote:
> On Thu, Jul 11, 2024 at 12:15:11PM +0100, Andrew Cooper wrote:
>> Archlinux is a rolling distro, and is subject to arbitrary changes as the
>> container is rebuilt.
> I disagree about the changes been arbitrary, it is just new version of
> software. :-)
>
> But I guess "arbirary changes" could be a description for package been
> removed from the main/official archive, and left for the users to build
> themselfs.

Specifically, rebuilding the container for staging has a side effect of
jumping the toolchain version under all stable trees.

I'll see about tweaking the wording.


>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Anyway:
> Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>

Thanks.

> (Next, automatically rebuild the container every month, I could probably
> revive my old patch series doing that)

That's also on the list, but not for 4.19.  Qemu rebuild their
containers as the first pipeline stage, and while I think that's
overkill, I was going to see if I could turn it into a weekly(?)
scheduled job.

~Andrew
diff mbox series

Patch

diff --git a/automation/gitlab-ci/build.yaml b/automation/gitlab-ci/build.yaml
index 3e299f34f461..1446bc1d0ea7 100644
--- a/automation/gitlab-ci/build.yaml
+++ b/automation/gitlab-ci/build.yaml
@@ -573,11 +573,13 @@  archlinux-gcc:
   extends: .gcc-x86-64-build
   variables:
     CONTAINER: archlinux:current
+  allow_failure: true
 
 archlinux-gcc-debug:
   extends: .gcc-x86-64-build-debug
   variables:
     CONTAINER: archlinux:current
+  allow_failure: true
 
 centos-7-gcc:
   extends: .gcc-x86-64-build