From: Christian Thalinger <twisti@complang.tuwien.ac.at>
To: mauve-patches ml <mauve-patches@sourceware.org>
Subject: Re: write XML output file only once
Date: Mon, 19 May 2008 08:09:00 -0000 [thread overview]
Message-ID: <1211184522.11614.18.camel@imac523d.theobroma-systems.com> (raw)
In-Reply-To: <1210847780.3214.24.camel@imac523d.theobroma-systems.com>
On Thu, 2008-05-15 at 12:36 +0200, Christian Thalinger wrote:
> Hi!
>
> This patch only writes the XML output file once after the Harness sends
> "_dump_data_" and not after each finished testlet. This can be a huge
> amount of data writes when running e.g. on java.util.
>
> OK to commit?
I'll commit that one now. For me this is a much better solution than
the current one because the current one is only better if the failing
test is the last one (think of running a lot of tests like java.util,
not just only one or two). When a test crashes or hangs Harness
restarts a new RunnerProcess and overwrites the previous XML file, so
all previous test data is lost anyways.
- twisti
prev parent reply other threads:[~2008-05-19 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 10:36 Christian Thalinger
2008-05-19 8:09 ` Christian Thalinger [this message]
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=1211184522.11614.18.camel@imac523d.theobroma-systems.com \
--to=twisti@complang.tuwien.ac.at \
--cc=mauve-patches@sourceware.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).