| Age | Commit message (Collapse) | Author |
|
|
|
Docutils 0.17 creates problem with our Sphinx rtd theme.
|
|
|
|
They should not be necessary today as they date from the shareable
pre-artifact epoch, an incur in an slowdown.
|
|
|
|
We introduce a new package structure for Coq:
- `coq-core`: Coq's OCaml tools code and plugins
- `coq-stdlib`: Coq's stdlib [.vo files]
- `coq`: meta-package that pulls `coq-{core,stdlib}`
This has several advantages, in particular it allows to install Coq
without the stdlib which is useful in several scenarios, it also open
the door towards a versioning of the stdlib at the package level.
The main user-visible change is that Coq's ML development files now
live in `$lib/coq-core`, for compatibility in the regular build we
install a symlink and support both setups for a while.
Note that plugin developers and even `coq_makefile` should actually
rely on `ocamlfind` to locate Coq's OCaml libs as to be more robust.
There is a transient state where we actually look for both
`$coqlib/plugins` and `$coqlib/../coq-core/plugins` as to support
the non-ocamlfind plus custom variables.
This will be much improved once #13617 is merged (which requires this
PR first), then, we will introduce a `coq.boot` library so finally
`coqdep`, `coqchk`, etc... can share the same path setup code.
IMHO the plan should work fine.
|
|
|
|
This seems to have been missed in
https://github.com/coq/coq/pull/13598
(16cd0d5cfc0c4702b8220dad8e91f31a89d904ba)
|
|
|
|
This fixes CI from their using the Stdlib module.
|
|
|
|
|
|
When we started using "needs" for the acyclic graph scheduling we
needed to duplicate dependencies and needs (I forgot if it was
documented or just buggy).
Nowadays gitlab doc https://docs.gitlab.com/ee/ci/yaml/#needs says
>In GitLab 12.6 and later, you can’t combine the dependencies keyword
with needs to control artifact downloads in jobs. dependencies is
still valid in jobs that do not use needs.
Some jobs in stage-1 had "dependencies: []" without a corresponding
"needs", not sure why as the only job in a previous stage is
docker-boot which has no artifacts to skip.
We don't want "needs: []" as that would fail to wait for the docker
image, so we just have nothing instead.
|
|
|
|
|
|
Checked by the linter so we don't forget to update it.
Also checked by before_script so we don't run jobs for nothing.
|
|
Reviewed-by: SkySkimmer
Ack-by: silene
|
|
|
|
In this way interval does not have to wait too much
|
|
|
|
|
|
|
|
|
|
|
|
instead of recursive make
|
|
Fixup #13050.
|
|
|
|
Reviewed-by: Zimmi48
|
|
git fetch --unshallow
Reviewed-by: SkySkimmer
|
|
We put dmesg.txt in the artifact path for all build-template users,
but only these 2 jobs produce it to avoid uploading unused data (see
discussion in #13043).
|
|
Reviewed-by: Zimmi48
|
|
|
|
|
|
After #8743 we don't depend on `num` anymore in the codebase; thus we
drop the dependency.
This could create problems for plugins relying on this implicit
linking.
|
|
Reviewed-by: Zimmi48
|
|
|
|
In particular, behavior of `Z.gcd` and `Z.lcm` has been fixed in
1.10, see
https://github.com/ocaml/Zarith/issues/58
|
|
In order to support the workflow where coqbot automatically turns
failing CI jobs into minimized examples for the test-suite easily
(https://github.com/coq/bot/issues/107), we want to be able to get all
of the .v files and all of the generated .vo and .glob files in the
artifact, even when the build fails.
|
|
- `odoc` must be bumped to support 4.11
|
|
|
|
We replace Coq's use of `Big_int` and `num` by the ZArith OCaml
library which is a more modern version.
We switch the core files and easy plugins only for now, more complex
numerical plugins will be done in their own commit.
We thus keep the num library linked for now until all plugins are
ported.
Co-authored-by: Vincent Laporte <Vincent.Laporte@fondation-inria.fr>
|
|
This focuses review requests to bench-maintainers instead of sharing
with ci-maintainers
|
|
Reviewed-by: SkySkimmer
Ack-by: ppedrot
|
|
Reviewed-by: ejgallego
|
|
Reviewed-by: ejgallego
|
|
|
|
|
|
Now that 4.11.0 is released the trunk job doesn't work.
4.12 also doesn't work for separate reasons ("No rule found for
kernel/byterun/byterun.a")
We will separately update the edge switch in the docker image to use 4.11.0.
|
|
|
|
|