Le 28/05/2026 à 13:00, Stéphane Glondu a écrit :
If I read [1] correctly the full source of ocaml-dune is copied to the
artifacts. Is that really intentional and useful? If so, please
explain and I can raise the limit for ocaml-dune. If not, can you
please orchestrate the test run differently such that only useful
artifacts are left in $ADT_ARTIFACTS at the end of the run?
Sorry, I must be missing something obvious... When are any artifacts
"useful"? Why are they "kept" in the first place?
Oh, I wasn't aware that "artifacts" were downloadable from
ci.debian.net... Everything is clear, now! Obviously, I was using
$ADT_ARTIFACTS instead of $AUTOPKGTEST_TMP (probably mimicking another
package). This bug is probably present in all my packages...
BTW, where are all these environment variables documented?
A fix is on its way.
Cheers,
--
Stéphane