Etienne Millon

#21381 took care of everything we can reasonably do in opam-repository.

I released ocaml-opam/opam-compiler 0.1.0 this morning using a freshly installed dune-release.1.4.0 and it returns `null`, so I don't think that's the reason.

> The downside is that there is no canonical S-expression parser: To remove any ambiguity, this means "no s-expression parser that is canonical", not ["parser of canonical s-expressions"](https://github.com/ocaml-dune/csexp).

I think you can adapt your message solution by adding a failing command to the build instructions if both conditions are set: ["false" {ocamlfind:version = "1.8.1" & ocaml:version = "4.05.0"]...

FYI @stevebleazard there's your token in that trace. I would advise revoking it (if github's token scrubbing didn't already find it)

See #286

I think that's an issue with your dune file - it won't copy `test/samples` under `_build/`. To do so, you can add the dependency by adding something like `(deps (glob_files...

A way to do that is to group the slow tests in a different executable, so that one can use `dune runtest tests/fast/` to only run fast ones (or do...

> where is this decision/check made? The reason is [here](https://github.com/mirage/mirage-tcpip/blob/65e07740e6a16bdae34c2d195e1eecac308359f3/test/dune#L15): `(action)` determines how the test executable is invoked by `dune runtest`. In that case, it is passing the `-q` flag...

:+1:, the canonical example would be ounit's `(>::)` (name a test) and `(>:::)` (name a test group).