Hi,
On 1/17/26 18:55, Paul Gevers wrote:
Now, I wouldn't deploy this without discussion, because I think visibility of the results isn't great. The blocks will show up on the global excuses page [1], is that enough for tracking migration of binNMU's and their autopkgtest results?
I discussed this in private, and I now think the visibility doesn't need to block the deployment. I think we saw this week a case where this MR could have prevented issues in testing: bug 1125777 on arm64. The src:gjs autopkgtest is triggered by src:mozjs140 and src:gnome-shell is triggered by src:gjs, both of which show the failure.
Some ideas that came up:* ben currently doesn't clearly show if successful rebuilds actually migrated, but it does already know which packages are in which suite; maybe it could additionally show the status for testing (my idea would be one column for testing, like the first one for unstable, maybe with a link to the excuses (see next point)). * the excuses.yaml could be processed and split into per transition pages; either by ben directly (although I can recognize if that's considered a far stretch for bens purpose), or by some stand-alone tool that takes the excuses.yaml and the machine readable ben output.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
