Hi, I firmly believe that reports must make issues obvious and should offer everything useful for digging in deeper. I don't think update_excuses.html does that: it mostly exposes micro-issues and makes you click several times before getting the information you need. It's britney's output re-formatted rather that we happen to use, not a tool designed for us.
Over the past several months, I've been working on a better frontend for it. There's an awful lot more to do but I feel it's already much better. I had been running it from my laptop but I've finally created a production environment for it last week: https://ubuntu.dcln.fr/update_excuses.html The typical update_excuses.html is fetch and rewritten into this page. The reason I don't use the YAML output is because it's not richer nor more structured than the HTML output, and I would be starting from a blank sheet, probably sometimes losing elements. Some of the improvements: a) tabular tests results make it easier to spot patterns (e.g. arch-related failures, but also tests failing on all arches) b) test results have an accompanying date (again, to spot patterns) c) re-written statuses because which I find much more detailed and explicit (e.g. when tests results are not available yet but migration reference failed and that test won't block the migration) d) don't merely display LP bug numbers but also bug title and last-update e) categories and matching package population report e.g. - needing attention (261) [ i.e. at least one test failed ] - blocked by another (61) [ requires another package to also migrate which is blocked ] - merely waiting (148) [ requires another package to also migrate which is not blocked (at least that's what britney says) ] - no issues so far (0) [ no test failed, so far ] - waiting for another item's results (3) [ see below ] - requiring approval (1) [ self-explanatory, now linux-nvidia which blocks the three above ] - Britney missing information (164) [ britney is waiting for something, most likely package builds, sometimes for a long time due to failed builds ] f) ability to hide categories, architectures or packages of some teams g) more up-to-date build status (not a big difference when britney takes 20 minutes to run but a much bigger one when it takes 6 hours) but also more detailed build status: rather than "missing", it can be success, failed, dependency wait and more h) list of packages ready to migrate but blocked by the current package And many more. I usually introduce changes after being frustrated by something. Updates are necessarily delayed compared to britney but only by a few minutes (hi launchpad team! sorry for the server load!). Code is hosted on gitlab: https://gitlab.com/adrien-n/update_excuses_rewriter Feature requests, comments and issue reports are welcome. Keep in mind that if you find something frustrating or painful, you're likely not the only one and many people are probably also slowed down by the same issues. The code is terrible right now, but the goal is to separate parsing current excuses and creating the new output and all will be much better (but that's when I feel confident all of britney's outputs are handled) PS: a lot of the work involved is to actually fully understand britney's output; it's likely that I've misunderstood some nuances and corrections are appreciated. -- Adrien -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
