Hi Paul,

Le 21/07/2024 à 08:18, Paul Gevers a écrit :
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.

That's fine for now. I guess you submitted via pasting the json you created in the self-service.

Indeed.

You get priority 10 that way by default. Did you we the service also has an API [1] you can use? The json for it is similar and it has a priority parameter. (@terceiro: does the self-service have an undocumented priority parameter, or is it really absent)?

I am aware of the API, but have not yet integrated it into my workflow.

Of course the cool thing you can do (and why I pointed you at britney2) is that you can also test for reverse (test) dependencies and check that *they* still work with the rebuild packages. Due to the way we do rebuilds in the archive (binNMU instead of NMU) we don't do those tests there (bug #944458), so it currently has added value if you could already check. To be clear, I'm not asking you to do it, I'm making you aware of these things, such that you can take it along if you so wish.

I've added packages that declare rebuilt packages in their testsuite-triggers field. That makes a total of 104 packages.

I've scheduled those packages, and it revealed 5 failures:
- bdebstrap: seems unrelated to OCaml (rather to Python I'd say)
- coq-unimath: expected (not rebuilt because of resource exhaustion)
- frama-c: to be investigated
- ocaml-rope: to be investigated
- opam: already investigated (see my previous mail)

PS: one other idea I'm having. There are multiple teams doing these kind of rebuilds and archive creation; does each have their own tools and does it their own way, I guess so? Has anybody ever tried to have the teams join forces? ruby, perl, python and ocaml I already know of. (I fear I'm hearing PPA/bicksheds/debusine resonating in my question).

I guess so, too. There is also (at least) haskell.

I've been working on my transition scripts since at least 2012 (first upload of ben to Debian). At that time, there was no tool suitable to prepare OCaml transitions with its idiosyncrasies. Since them, I incrementally improve them at each OCaml transition.

I tried to make my scripts generic:


https://salsa.debian.org/debian/ben/-/tree/master/examples/transition-scripts

If anybody wants to use them in another context, I can help. But it would seem incongruous to me to promote my own tools to other circles without knowing their needs and workflows.


Cheers,

--
Stéphane

Reply via email to