Santiago Vila:
This is awesome work! I hope you can start the MBF soon.One minor comment:* 862 failures - Of these 217 failed with an error related to this change - The remaining failed for other reasons (including running out of memory on the host, etc.)I'd like to look at those "remaining". Can you put the list somewere? When I test for packages which fail if "some special condition is met"(for example, make --shuffle) I usually try to do two groups: Packages which fail with the condition and packages which would fail anyway, and I try to be sure in which group each package is, so maybe I could try to fill the missinggaps here. Thanks.
I do not have a curated/pruned list of those packages at hand, since they were not my priority.
I did a quick naive query in [ignored-problems.list] as a quick approximation, which will have failures that I retried and infrastructure issues (like OOM) plus it misses a few failures that I did not fully "classify". Manually review of the log concluded they were ignorable, but I did not have a good regex for them, so the tool thinks they are unclassified.
I have also uploaded the underlying sqlite database I used at [db.sqlite3]. The database was created with https://salsa.debian.org/stefanor/debusine-rebuilds/. I do not think the tooling there will help you for the data analysis you need.
If you look into the database, I think you would need all source paackages from `srcpkg` where the latest build per source package (subquery on `build`) and then LEFT JOIN with `problem` to find packages without a problem OR with a problem that was ignored (plus also filtering `build.architecture != 'amd64'` because I scheduled a bunch of packages on the wrong architecture by mistake at some point). Though, I am not in the mental space for writing and debugging that query, so I will leave that to the readers. :)
I think I got most of the logs from debusine into the logs folder. Though, if you should need a log I was missing, they should still be available for another 14-21 days (depending on the build). Find the `build.work_request_id` for the build and insert into the URL
https://debusine.debian.net/debusine/work-request/{ID}/That will give you a page with the log (under "Output artifacts"), build status (etc.). Example: https://debusine.debian.net/debusine/work-request/57852/
(If you need logs of logs, have a look at the debsuine-rebuild's "log-download" command to see how it finds the URL).
That is the best I can offer here, so I hope it was useful. Best regards, Niels [ignored-problems.list]: https://people.debian.org/~nthykier/rrr-no-as-default/docs/ignored-problems.list [db.sqlite3]: https://people.debian.org/~nthykier/rrr-no-as-default/docs/db.sqlite3
OpenPGP_signature.asc
Description: OpenPGP digital signature
