From: Mark Wielaard <mark@klomp.org>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: frysk@sourceware.org
Subject: Re: TestLeakingFileDescriptor
Date: Tue, 31 Jul 2007 11:00:00 -0000 [thread overview]
Message-ID: <1185879622.3653.80.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20070731021143.GD22305@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Hi Kris,
On Mon, 2007-07-30 at 22:11 -0400, Kris Van Hees wrote:
> I'd like to propose that the TestLeakingFileDescriptor test cases be marked
> as stress tests rather than regular tests, to avoid them being executed at
> every testsuite invocation. Reason for this proposal is two-fold: first of
> all, these tests are implicitly intermittent due to the fact that they depend
> on a behaviour that is not deterministic (the garbage collector does not
> actually do I/O resource mangement), and secondly, when they do fail they tend
> to cause a bunch of side effects (causing later tests to fail, causing daemon
> instances of TestRunner to never get torn down, ...).
I think that is a good idea since the test results are pretty flaky as
they are now making comparing test runs pretty hard. I known good set of
tests that always PASS and that you don't have to second guess would be
really helpful. Only issue I can see is that if the stress tests are
optional people will never run them, but I guess that is what the
autobuilder/tester is for.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-31 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 2:13 TestLeakingFileDescriptor Kris Van Hees
2007-07-31 11:00 ` Mark Wielaard [this message]
2007-07-31 13:35 ` TestLeakingFileDescriptor Andrew Cagney
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=1185879622.3653.80.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=kris.van.hees@oracle.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).