Suggestion for a new GNATS policy

Daniel Berlin dberlin@dberlin.org
Mon May 12 18:57:00 GMT 2003


On Monday, May 12, 2003, at 12:33  PM, Steven Bosscher wrote:

> Op ma 12-05-2003, om 16:39 schreef Wolfgang Bangerth:
>>> I can make a radio button labeled "Reconfirm" (right under "Leave as
>>> NEW") for you  guys if you want, so it's just "select reconfirm, 
>>> click
>>> commit".
>>
>> That's cool. I also like the "minimized" and "verified" flags (which
>> indeed are really boolean flags).
>>
>> Thanks for you work and responsiveness on all this, Daniel!
>
> Wild idea:
>
> What I'd really like to see is a "minimized test case" field (which may
> be a pointer to an attachment) and an SQL query to extract them all.

Errr, you can have flags on attachments, so you can mark attachments 
with a  "minimized test case" flag, and query all of the existing ones.

It takes about 7 lines of perl to extract them:

# Include the Bugzilla CGI and general utility library.
use lib qw(.);
require "CGI.pl";

# Establish a connection to the database backend.
ConnectToDatabase();
use Bugzilla::Flag;
use Bugzilla::FlagType;
my (%criteria);
$criteria{"target_type"} = "attachment";

#This is the minimized flag id
$criteria{"type_id"} = "3";
my @results = Bugzilla::Flag::match(\%crit);


>
> That way, people could put DejaGNU-ified test cases in the bug 
> database,
> rip them all out with the query, and test them on their target.  Even 
> if
> only a few people would to that, we would know much sooner if/when a 
> bug
> got fixed unnoticed (ie. PR not in CVS commit msg.), and to which 
> target
> the bug applies.
>
> The idea is that we really would like to be able to batch-test PR
> reports.  Janis and Wolfgang have talked about a PR testsuite, and this
> idea was mentioned again earlier in this thread, but we really don't
> want to litter the test suite that much.  With an easy way to extract
> all minimized test cases, you'd effectively have the same thing without
> even touching the testsuite.
>
> Thoughts?
>
> Greetz
> Steven
>
>



More information about the Gcc mailing list