[rfa/testsuite/PING] asm-source.exp: use UNTESTED
Andrew Cagney
cagney@gnu.org
Mon Jan 5 21:49:00 GMT 2004
> 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
More information about the Gdb-patches
mailing list