public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/65205] New: Wrong dh-shouldfail usage in OpenACC libgomp tests
@ 2015-02-25 14:01 tschwinge at gcc dot gnu.org
  2015-04-30 12:45 ` [Bug testsuite/65205] Wrong dg-shouldfail " tschwinge at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: tschwinge at gcc dot gnu.org @ 2015-02-25 14:01 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65205

            Bug ID: 65205
           Summary: Wrong dh-shouldfail usage in OpenACC libgomp tests
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Keywords: openacc
          Severity: major
          Priority: P3
         Component: testsuite
          Assignee: jnorris at gcc dot gnu.org
          Reporter: tschwinge at gcc dot gnu.org

A bunch of the OpenACC libgomp tests that we added are expected to terminate
with an error exit status, and printing specific error message.  For a lot of
them, we wrongly just used dg-shouldfail directives to codify this, providing
the expected error message as the comment argument to dg-shouldfail.  Separate
dg-output directives should be used instead, so that we can detect if the test
case actually does fail, but not for the expected reason (that is, with the
specific error message).  (See
libgomp/testsuite/libgomp.oacc-fortran/data-already-1.f, for example.)


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-05-05  9:40 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-25 14:01 [Bug testsuite/65205] New: Wrong dh-shouldfail usage in OpenACC libgomp tests tschwinge at gcc dot gnu.org
2015-04-30 12:45 ` [Bug testsuite/65205] Wrong dg-shouldfail " tschwinge at gcc dot gnu.org
2015-04-30 13:10 ` tschwinge at gcc dot gnu.org
2015-05-05  9:40 ` tschwinge at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).