From: Noa Resare <noa@resare.com>
To: Mauve Discuss <mauve-discuss@sources.redhat.com>
Subject: gnu/testlet/java/nio/channels/FileChannel/manyopen.java broken
Date: Fri, 08 Oct 2004 06:35:00 -0000 [thread overview]
Message-ID: <1097217312.1324.43.camel@localhost.localdomain> (raw)
gnu/testlet/java/nio/channels/FileChannel/manyopen.java tries to open
1024 * 3 files and signals failure if that fails.
I don't think it can be considered an error if this fails, especially
since many popular operating systems limit the number open files that a
single process can have:
Here is the output of "ulimit -n" on some boxes I have access to:
OpenBSD 3.4 x86: 64
Solaris 9 sparc: 256
Linux (debian 2.2 x86/suse 8 AMD64/Fedora core 1/2/3) : 1024
FreeBSD 4.10-BETA: 7322
NetBSD 1.6.1: 64
OSX 10.2: 256
Since the test doesn't actually test for anything other than the ability
to open many files and the extent of that ability isn't specified in any
spec that I'm aware of I suggest that we remove the test.
/noa
next reply other threads:[~2004-10-08 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 6:35 Noa Resare [this message]
2004-10-08 6:47 ` Stephen Crawley
2004-10-08 10:05 ` Mark Wielaard
2004-10-08 11:07 ` Noa Resare
2004-10-08 17:00 ` Thomas Zander
2004-10-11 0:50 ` Stephen Crawley
2004-10-11 6:39 Jeroen Frijters
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=1097217312.1324.43.camel@localhost.localdomain \
--to=noa@resare.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).