From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite/PING] asm-source.exp: use UNTESTED
Date: Mon, 05 Jan 2004 21:49:00 -0000 [thread overview]
Message-ID: <3FF9DC05.5060704@gnu.org> (raw)
In-Reply-To: <20040105210335.912984B35A@berman.michael-chastain.com>
> ac> However, remember why this test was originally changed to fail messy -
> ac> the test was being skipped and, as a demonstratable consequence,
> ac> everyone chose to ignore it rather than fix the testcase :-(
>
> Well, I'm choosing to ignore it for native hppa2.0w-hp-hpux11.11,
> until after function calls work, and C++ works, and the internal
> hp_aCC_compiler variable works, and the other 200 ERRORs and
> 2000 FAILs have gotten some attention.
>
> It's just annoying to open up gdb.log and the first 4 ERRORs and 5
> WARNINGs are things that I know I won't fix this month. I keep having
> to look past this to get to more important problems.
>
> ac> What about UNTESTED, and then KFAIL everything? Knowing my luck that
> ac> will be much harder than it seems ...
Prior to "gdb_supress_entire_file", what was this test reporting when
the code was missing?
> That's what gdb_suppress_entire_file is supposed to do now, but it
> doesn't work. It sets a little state variable that is supposed to FAIL
> every test in the current file. But I still get a slow of
> ERROR/WARNING on top of the 28 FAILs.
>
> If I can't change asm-source.exp, I guess I'll just keep ignoring
> the results by hand. At least it's not incurring timeouts.
Andrew
next prev parent reply other threads:[~2004-01-05 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 21:03 Michael Elizabeth Chastain
2004-01-05 21:49 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-02 20:57 Michael Elizabeth Chastain
2004-01-05 15:41 ` Andrew Cagney
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=3FF9DC05.5060704@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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