For the captures that are autogenerated and creates a crash and are
added as a bug automatically to bugzilla, since there are potentially
several reports for the same crash
(and some crashed can only ge reproduced on some platforms (some of
the crash captures did not generate a fault on my box for example)).
Would it be possible to have a script that would test those crash
captures automatically after the next time ethereal is rebuilt by the
buildbot and if the same platform/buildbot box does no longer create a
crash then the buildbot will automatically close the bug?
I.e. buildbot on platform X discovers a crash bug and creates a bug
in bugzilla.
Maybe it also adds some text to the bug "Bug reported by buildbot:X,
do not close, buildbot for X will automatically close the bug when it
no longer occurs".
Next time buildbot X rebuilds a new ethereal it will test if this bug
is still present.
If not, the buildbot will automaticaly close the bug.
?
On 4/22/05, Gerald Combs <gerald@xxxxxxxxxxxx> wrote:
> It looks like everyone's settled on Bugzilla for bug tracking. I'm
> going to start tearing down the Trac and Roundup installations and
> tweaking Bugzilla to make it a little easier to use and less ugly.
>
> We need to address the problem of notifying people about new bugs.
> Bugzilla generates a LOT of mail, so I don't think we should simply
> point it at ethereal-dev. Should an "ethereal-bugs" list be set up?
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
