[Debian-salsa-ci] replace reprotest by debrebuild
Otto Kekäläinen
otto at debian.org
Mon Nov 24 18:18:59 GMT 2025
Hi!
> * Otto Kekäläinen <otto at debian.org> [2025-11-24 09:51]:
> >I was trying to browse the results at
> >https://reproduce.debian.net/all/stats/forky/#failed-to-reproduce and
> >looked at failed ones, but I don't know even how to read the log. For
> >example package 'mono' failed to reproduce but I don't see any issues
> >in the log at https://reproduce.debian.net/all/api/v1/builds/117850/log.
>
> Have a look at the diff linked below the 💠 or here:
Ah indeed, thanks for pointing out the diffoscope link. The UI is very
confusing with this line: 💠🍥🔬# mono-libraries 💠🍥🔬🗈
Maybe present these as a table or a list, use tooltips etc.
>
> https://reproduce.debian.net/all/#mono-libraries
On the page above I do see the diffostop link very clearly. However on
another bad one (https://reproduce.debian.net/riscv64/forky.html)
there is a link only to the log, but not to diffoscope. Perhaps it
should have placeholders to all the link that page can have, but then
state just something like "not generated yet" so people browsing can
figure out that the link would be there if it existed.
Also it is confusing that the pages use anchor links:
https://reproduce.debian.net/all/#mono-libraries
If would be more aligned with web app semantics to use full path:
https://reproduce.debian.net/all/mono-libraries
Anchor links should be used only to link to a anchor within a page.
Anyway, I understand this is all in development and new, and it will
for sure evolve. Just sharing my initial reaction/feedback.
And I see Santiago is reviewing the MR so things are progressing for
Salsa CI as well. If you want to have more reviewers/testers, you
could maybe reach out to the people who previously filed Salsa CI
issues or merge requests on the same topic.
Keep up the good work,
Otto
More information about the Debian-salsa-ci
mailing list