Hi,
Le 20/07/2024 à 21:24, Paul Gevers a écrit :
Thanks. I've triggered test of camlbz2 with ocaml-next. It does seem
to work :-)
Great, so next is some expectation. You're free to use this service, but
if you schedule lots of tests (hundreds), please use an appropriate low
priority, to not interfere too much with security (prio 9) and migration
testing (prio 5).
I've scheduled tests of all OCaml packages that provide tests (there are
86 of them). I did not specify any priority, I hope that's fine.
It did allow me to spot a regression in camlzip, which I've already fixed.
I also noticed that opam's tests were broken, but they have been for a
while so this is not a regression. I am in the process of packaging a
new version (which depends on a package still in NEW), I will fix that
on the way.
Other than these two outliers, all jobs succeeded :-)
If your interested, you could also use the release team's britney2
scripts to schedule all reverse tests. E.g. the security team uses it
too:
https://salsa.debian.org/security-team/britney2/-/blob/master/scripts/autopkgtests.md?ref_type=heads
I used:
https://salsa.debian.org/debian/ben/-/blob/master/examples/transition-scripts/examples/ocaml/gen-ci-json.ml
to generate a JSON that I submitted to ci.debian.net.
This tests only packages that have been rebuilt and have a "testsuite"
field, and pins all build-dependencies that have been rebuilt.
I'm pretty confident now that this transition is manageable and should
not pose big issues.
Cheers,
--
Stéphane
