This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch/rfc] Remove all setup_xfail's from testsuite/gdb.mi/


Daniel writes:
> Associating a PR with them is a different issue.  Just because we
> associate a PR doesn't mean we have to use KFAIL.

Fernando writes:
> That is correct.  The last argument of a setup_xfail, if it does not
> contain '-' (Argh!  Don't blame me, it was already there since immemorial
> times) is the PR number.  It can easily be a gdb/NNN bug id.  We cannot
> enforce the syntax, but we can enforce it as a police.

Okay, I can live with that.  As long as there is a *gdb* bug id on it;
that is the important part to me.

For the mechanics, we can set 'class=suspended', or maybe we can add a
new class to gnats.

> Why doing this?  A script can go through the KFAILs (for each platform)
> and, by reading the Gnats database, automatically create a KNOWN BUGS
> man page section, or a section of a Release Notes document.

Right now, I do this for native i686-pc-linux-gnu for every release
candidate.  So it helps a lot when all KFAIL's and XFAIL's point to
a place where we can write analysis notes.

> P.S.: Does someone know how to programatically access the Gnats database?

I don't know.  You could do screen scraping with URL's like the ones
that I post in the sunday project reports.

Michael C


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]