From: Omair Majid <omajid@redhat.com>
To: mauve-discuss@sources.redhat.com
Subject: Issue with XML output when RunnerProcess is killed
Date: Tue, 17 Feb 2009 18:33:00 -0000 [thread overview]
Message-ID: <499B02F0.3020206@redhat.com> (raw)
Hi,
I ran across an issue with mauve's xml output today. The xml test
results are stored in a TestReport object which belongs to
RunnerProcess. In tests where Harness thinks that the RunnerProcess has
timed out, it kills RunnerProcess, causing the TestReport object to be
destroyed and all the information to be lost. I am not sure how to go
about fixing this. Any ideas?
Thanks,
Omair
reply other threads:[~2009-02-17 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=499B02F0.3020206@redhat.com \
--to=omajid@redhat.com \
--cc=mauve-discuss@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).