public inbox for mauve-patches@sourceware.org
 help / color / mirror / Atom feed
From: Omair Majid <omajid@redhat.com>
To: mauve-patches@sources.redhat.com
Subject: [PATCH] Output xml results for tests with compilation problems
Date: Tue, 17 Feb 2009 14:46:00 -0000	[thread overview]
Message-ID: <499ACDAB.1070805@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 862 bytes --]

Hi,

When mauve fails to start a test which because of compilation problems,
no xml output is gnenerated:

$ java Harness -vm /usr/bin/java
gnu.java.security.hash.TestOfHashFactory -xmlout output.xml
FAIL: gnu.java.security.hash.TestOfHashFactory
     exception when loading:
      java.lang.Error: Unresolved compilation problems:
	The import gnu.java cannot be resolved
	The import gnu.java cannot be resolved
	IMessageDigest cannot be resolved to a type
	HashFactory cannot be resolved
	HashFactory cannot be resolved
[snip]

The xml output file contains no failures:
<?xml version='1.0' encoding='UTF-8'?>
<testreport version='0.1'>
     <jvm name='Sun Microsystems Inc.'
       version='14.0-b08'
       os='Linux 2.6.27.9-159.fc10.i686 i386' />
</testreport>

The attached patch fixes mauve so that a failure is reported in the xml
file.

Cheers,
Omair




[-- Attachment #2: xmloutput-on-failed-to-compile-tests.patch --]
[-- Type: text/plain, Size: 374 bytes --]

--- RunnerProcess.java	11 Jun 2008 10:08:00 -0000
+++ RunnerProcess.java	13 Feb 2009 16:50:41 -0000
@@ -362,6 +362,10 @@
         if (verbose)
           System.out.println("TEST FAILED: exception when loading "
                              + stripPrefix(name));
+
+        if (report != null)
+          report.addTestResult(currentResult);
+
         return;
       }
 


             reply	other threads:[~2009-02-17 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 14:46 Omair Majid [this message]
2009-02-19 19:02 ` Lillian Angel
2009-02-19 19:44   ` Omair Majid

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=499ACDAB.1070805@redhat.com \
    --to=omajid@redhat.com \
    --cc=mauve-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).