-
As of writing, Coq latest in our CI runs is still 8.19.1, but Coq dev jumped from 8.20 to 8.21+alpha.
The problems occur in the satellites TypeTheory and SetHITs.
This became manifest for PR #1891, …
-
In Coq Platform CI (which is heavily opam based) I see a change in behaviour after updating to opam 2.2: when I pin a package to the version it already has, opam upgrades all packages depending on thi…
-
> > Doesn't Coq CI check coqchk though?
>
> By default coqchk ignores the VM data.
Maybe we should enable the VM on the CI?
_Originally posted by @JasonGross in https://github.c…
-
In CI, it was visible that Coq dev (an alpha version of Coq 8.21) does not compile this satellite, but it is even worse.
-
We've been timing out a bunch on Coq's CI recently, and I imagine #368 makes things a bit worse (though not much worse). Perhaps we should offer some target that does not build everything for Coq's CI…
-
Hi folks,
I'd be great if I could add Alectryon to Coq SerAPI's CI, so I can test it not being broken by new SerAPI releases.
I guess I need:
- the recipe to build Alectryon from a local SerAPI…
-
There is a "dev" package pick, which builds what is in opam dev, but this frequently does not work. It would make sense to have a pick which automatically creates patched opam packages matching Coq's …
-
https://github.com/rems-project/cerberus/commit/20d9d5ce2e982c4744ef6911a25a3be9307518f3 fixed the existing CN lemma tests, but these should really be part of the CI. This requires re-working the CI s…
-
Cf. https://github.com/UniMath/UniMath/actions/runs/8435960904/
Coq latest has a 10 minutes build of the satellite, while Coq dev takes 32 minutes.
-
It's quite hard to spot misformalizations when reading the formalization alone.
It would be great if the $$\LaTeX$$ description could be included in a docstring (`/-- doc -/` in lean, I can't speak f…