On 07/29/14 12:35, David Malcolm wrote:
At Cauldron on the Sunday morning there was a Release Management BoF
session, replacing the specRTL talk (does anyone know what happened to
the latter?)
One of the topics was bug triage, and how many bug reports lacked basic
metadata on e.g. host/build/target, reproducer etc.
I suggested we could automate gathering this, and rashly promised to
write a prototype in Python. So here it is...
The attached script demonstrates a way to generate a URL that, when
followed, takes the user to the GCC Bugzilla "Enter Bug" page, with all
pertinent fields prepopulated with meaningful data. (run the script,
and follow the URL; this uses the same server-side URLs as the "Remember
values as bookmarkable template" BZ button).
The idea is that the "gcc" driver program could gain a --report-bug
feature that injects -save-temps into the options, disables plugins, and
tries to reproduce a crash. It then gives you the URL to click on,
capturing the backtrace and embedding it into the form for you.
Perhaps we could guess the "Component" based on the backtrace.
I note that there doesn't seem to be a "trunk" entry for "Version".
I am both proud of, and scared of, this idea: it could make it easy for
people to file higher-quality bugs. On the other hand, that means more
bugs in the tracker... (they do at least need to be logged in).
Note that this points users at the GCC bug tracker. Presumably
downstream packagers of GCC may want to customize such a feature to
point at their bug trackers (e.g. at Red Hat we have our own bugzilla
instance, with a different set of custom fields).
So the obvious question is how does this relate to Jakub's patch that
Maxim @ Samsung is trying to get reviewed?
Jeff
