Mark Elvers

The error message was ``` 2024-09-06 16:41.22: New job: git fetch https://github.com/mirage/charrua.git#refs/pull/127/head (05c0d9f23a205adac8b96b3797725a03198e4677) 2024-09-06 16:41.22: Exec: "git" "-C" "/var/lib/ocurrent/var/git/charrua.git-1fa4fc8af49ffe3746b2b001c3e85fd74b863ef95f109aed21765682489d9720" "branch" "-f" "fetch-05c0d9f23a205adac8b96b3797725a03198e4677" "05c0d9f23a205adac8b96b3797725a03198e4677" fatal: not a valid branch point: '05c0d9f23a205adac8b96b3797725a03198e4677'...

The workers themselves are all running Ubuntu. When you see something like `debian-12-4.14_s390x_opam-2.2` this is a `runc` container running Debian 12 running on top of an Ubuntu s390x machine. We...

> The CI failures are just [debian-12-4.14_x86_32_opam-2.1 (failed: Failed: Build failed)](https://ocaml.ci.dev/github/ocurrent/opam-repo-ci/commit/d8ac120af81c2d22f03000ec3dc170c1d12faf21/variant/debian-12-4.14_x86_32_opam-2.1/-/refs/heads/shon/infra-320/vendors-to-pins), which are not be filtered out as I'd expect given [ocurrent/ocaml-ci#932](https://github.com/ocurrent/ocaml-ci/pull/932), even tho it _is_ being filtered out for...

I also note that this change significantly increases the build time on my system. ``` $ git checkout master && rm -rf _build/ && time dune build Switched to branch...

Yes, I did comment on @benmandrew thread that the `var` exclusion for Dune was indeed the issue. CI looks clean with the current build.

Looks good to me. I'd just wait for a quiet moment and deploy it. Any running jobs will be cancelled when the docker container is replaced.

Can you give an example of the two different behaviours you are seeing?

scyleia currently has a serious hardware fault which is under investigation

This process has been stalled as, after the upgrade to 24.04, ainia was unable to complete basic things, like building OCaml. Firmware updates on `ainia` have fixed it. (https://github.com/tarides/infrastructure/issues/331) Firmware...

This looks like a GCC compiler version issue. Are you using GCC 14? Have a look at this issue https://github.com/ocurrent/docker-base-images/issues/279 and the patches I created in the fork of opam-repository....