From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gcc-patches@gcc.gnu.org
Cc: java-patches@gcc.gnu.org
Subject: [libjava] XFAIL sourcelocation (PR libgcj/55637)
Date: Thu, 20 Feb 2014 12:05:00 -0000 [thread overview]
Message-ID: <ydda9dm7zwb.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
The libjava sourcelocation output test has been FAILing on mainline for
more than a year, with no sign of anything happening to resolve that.
To reduce testsuite noise, I suggest to XFAIL the test. In all mainline
test results from february, only a single set of testresults that
included libjava results (for ia64-suse-linux-gnu) didn't show those
failures.
Tested with the appropriate runtest invocations on i386-pc-solaris2.11
and x86_64-unknown-linux-gnu.
Ok for mainline?
Rainer
2014-02-20 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
PR libgcj/55637
* testsuite/libjava.lang/sourcelocation.xfail: New file.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: libjava-testsuite-sourcelocation-xfail.patch --]
[-- Type: text/x-patch, Size: 353 bytes --]
# HG changeset patch
# Parent 6fd38b9012dee330d1343765cfe3cd0e06f33d33
XFAIL sourcelocation (PR libgcj/55637)
diff --git a/libjava/testsuite/libjava.lang/sourcelocation.xfail b/libjava/testsuite/libjava.lang/sourcelocation.xfail
new file mode 100644
--- /dev/null
+++ b/libjava/testsuite/libjava.lang/sourcelocation.xfail
@@ -0,0 +1,1 @@
+xfail-output
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next reply other threads:[~2014-02-20 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 12:05 Rainer Orth [this message]
2014-02-20 13:49 ` Bryce McKinlay
2014-02-20 14:06 ` Rainer Orth
2014-03-30 10:18 Dominique Dhumieres
2014-03-30 21:10 ` Rainer Orth
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=ydda9dm7zwb.fsf@lokon.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).