public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: frysk@sourceware.org
Subject: Re: TestLeakingFileDescriptor
Date: Tue, 31 Jul 2007 13:35:00 -0000	[thread overview]
Message-ID: <46AF3AB5.7030703@redhat.com> (raw)
In-Reply-To: <20070731021143.GD22305@oracle.com>

It is very hard to comment on a technical when the technical background 
is limited.  Can you please provide an example of the problem, perhaps 
reduced to an automated test-case?  As they say, they pass for me.

Is your testbed the motivation behind this request?  We can certainly 
explore options such as moving some of the tests to the stress 
test-suite; however the quid-pro-quo is that we have also analyzed 
failing cases identified by the stress test and added deterministic 
fixes for them.

Andrew

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, ...).
>
> 	Cheers,
> 	Kris
>   

      parent reply	other threads:[~2007-07-31 13:35 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 ` TestLeakingFileDescriptor Mark Wielaard
2007-07-31 13:35 ` Andrew Cagney [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=46AF3AB5.7030703@redhat.com \
    --to=cagney@redhat.com \
    --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).