Closed palmskog closed 2 years ago
IIUC, @erikmd will fix this issue soon: https://github.com/coq-community/docker-base/pull/17#issuecomment-1084946566
Hi @palmskog @pi8027, Yes, thanks, I'm working on a fix.
To summarize one of the issues that occur:
coqorg/coq:dev
FTBFS. So mathcomp*:coq-dev
was stuck with opam 2.0.coqorg/base:bare
had already opam 2.1.2.mathcomp-dev
's Dockerfile, we ended up with an (opam binary, opam switch) incompatibility.Normally, this issue is fixed now. Feel free to reopen otherwise
@palmskog FWIW, the cron worklfow that was part of docker-coq-action's CI had spotted this issue (albeit I hadn't seen the failure e-mail before you opened this :)
Anyway, I'll take this opportunity to add yet another test in that workflow.
I still see this issue here in the following images:
Recompilation of MathComp happens in some other images (e.g., mathcomp/mathcomp:1.12.0-coq-8.13) too, but for different reasons, it seems.
@erikmd the problem seems to be with num
:
+ (script @ line 12) $ opam install --confirm-level=unsafe-yes -j 2 coq-mathcomp-apery --deps-only
<><> Synchronising pinned packages ><><><><><><><><><><><><><><><><><><><><><><>
[coq-mathcomp-apery.dev] synchronised (no changes)
The following actions will be performed:
- install seq base
- install conf-perl 2
- recompile num 1.3* [upstream or system changes]
- install re 1.10.3
- install camlp5 7.14
- recompile sexplib v0.14.0 [uses num]
- recompile coq 8.13.2* [uses num]
Is maybe some system package that num uses getting upgraded?
Hi @pi8027 @palmskog, well spotted, thanks for the report.
So it seems the culprit is this commit https://github.com/ocaml/opam-repository/commit/03ab8c0bebc78578f20718b3ff4f6e7c1285912c
There's only one solution in this case: recompiling the images; I'll look after this tonight after my last meeting.
@pi8027 @palmskog Rebuild done:
If a similar issue occurs again (e.g. if you experience a CI slowdown because a pinned package is recompiled (here, because of major changes in opam-repository packages; beforehand, because of an opam version mismatch)), feel free to open a new issue.
Since April 1, 2022, I'm seeing CI failures for a bunch of MathComp-related projects using the
mathcomp-dev
Docker image, for example here for RegLang.The failure happens during recompilation of Coq, which I believe should not be happening in the first place. Specifically, we first see the following version mismatch between opam 2.0 and opam 2.1:
Then, we get the recompilation during a package install:
Finally, Coq compilation fails due to lack of Dune(?):
This is likely related to the base image upgrade to opam 2.1 (cc: @gares).