From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, fnasser@redhat.com
Subject: Re: RFC: KFAIL DejaGnu patch
Date: Fri, 05 Apr 2002 17:40:00 -0000 [thread overview]
Message-ID: <3CAE5220.8090001@cygnus.com> (raw)
In-Reply-To: <20020405201029.A6868@nevyn.them.org>
> On Fri, Apr 05, 2002 at 07:29:54PM -0500, Fernando Nasser wrote:
>
>> Well, I am attaching the DejaGnu changes for KFAILs.
>>
>> Rob: can you please take a look, specially in the documentation
>> changes and see if they are fit for the master repository?
>>
>> Michael Chastain: Will you be willing to help me test this?
>> I've tried it and it seems to work. Yours scripts must also
>> be happy with it.
>>
>> Best regards,
>> Fernnado
>>
>>
>> P.S.: I was trying to find some test to try the setup_kfail on. I went
>> looking for the setup_xfail *-*-* calls but most don't have any comment
>> why they are marked like that. Then I've tried looking for the FAILs
>> and see if I could find a bug entry for those -- but it is not a
>> trivial task. I guess we will need everybody's help and memories to
>> gradually have things properly documented and related to the bug
>> entries.
>
>
> Looks good to me. Fernando, could I persuade you to write up a
> GDB-specific list of what each of the DejaGNU result codes is meant to
> cover? We could stick it in testsuite/ somewhere.
I had a similar suggestion in mind but not ``in testsuite/ somewhere''.
See:
http://sources.redhat.com/gdb/onlinedocs/gdbint_16.html#SEC154
(just making a note that testsuite/gdb.gdb/ isn't documented)
Andrew
next prev parent reply other threads:[~2002-04-06 1:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 9:53 RFC: KFAILs [Was: [RFA/mi-testsuite] XFAIL mi*-console.exp] Michael Elizabeth Chastain
2002-04-05 10:22 ` Daniel Jacobowitz
2002-04-05 13:45 ` Andrew Cagney
2002-04-05 13:51 ` Daniel Jacobowitz
2002-04-05 10:23 ` Fernando Nasser
2002-04-05 16:32 ` RFC: KFAIL DejaGnu patch Fernando Nasser
2002-04-05 17:05 ` Andrew Cagney
2002-04-07 16:25 ` Rob Savoye
2002-04-05 17:10 ` Daniel Jacobowitz
2002-04-05 17:40 ` Andrew Cagney [this message]
2002-04-08 8:37 ` Fernando Nasser
2002-04-07 16:29 ` Rob Savoye
2002-04-07 22:05 ` Eli Zaretskii
2002-04-08 8:22 ` Rob Savoye
2002-04-08 8:52 ` Fernando Nasser
2002-04-08 9:01 ` Rob Savoye
2002-04-08 8:41 ` Fernando Nasser
2002-04-08 9:00 ` Rob Savoye
2002-04-08 13:55 ` Andrew Cagney
2002-04-08 16:21 ` Rob Savoye
2002-04-08 16:34 ` Andrew Cagney
2002-04-08 16:48 ` Rob Savoye
2002-04-08 16:58 ` Andrew Cagney
2002-04-08 17:09 ` Rob Savoye
2002-04-08 23:58 ` Eli Zaretskii
2002-04-09 7:38 ` Rob Savoye
2002-04-08 23:53 ` Eli Zaretskii
2002-04-09 7:06 ` Daniel Jacobowitz
2002-04-05 16:51 Michael Elizabeth Chastain
2002-04-05 17:57 Michael Elizabeth Chastain
2002-04-06 14:40 Michael Elizabeth Chastain
2002-04-07 9:10 Michael Elizabeth Chastain
2002-04-07 18:41 Michael Elizabeth Chastain
2002-04-08 9:57 Michael Elizabeth Chastain
2002-04-08 10:34 Michael Elizabeth Chastain
2002-04-08 11:38 ` Daniel Jacobowitz
2002-04-09 7:50 ` Rob Savoye
2002-04-08 11:56 Michael Elizabeth Chastain
2002-04-09 9:13 Michael Elizabeth Chastain
2002-04-09 9:34 ` Rob Savoye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CAE5220.8090001@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox