From: Christian Thalinger <twisti@complang.tuwien.ac.at>
To: mauve-patches ml <mauve-patches@sourceware.org>
Subject: increase timeout in java.net.ServerSocket.AcceptTimeout
Date: Mon, 01 Sep 2008 09:39:00 -0000 [thread overview]
Message-ID: <1220261943.11930.3.camel@cthalinger> (raw)
Hi!
The java.net.ServerSocket.AcceptTimeout test failed consistently on
IcedTea with CACAO. I talked to Mark about it, as he's the author of
the test, and he said we should increase the ServerSocket timeout. It
seems to fix the issue.
- twisti
---
Index: ChangeLog
===================================================================
RCS file: /cvs/mauve/mauve/ChangeLog,v
retrieving revision 1.2125
diff -u -3 -p -r1.2125 ChangeLog
--- ChangeLog 25 Aug 2008 15:13:14 -0000 1.2125
+++ ChangeLog 1 Sep 2008 09:34:33 -0000
@@ -1,3 +1,8 @@
+2008-09-01 Christian Thalinger <twisti@complang.tuwien.ac.at>
+
+ * gnu/testlet/java/net/ServerSocket/AcceptTimeout.java (test):
+ Increase timeout from 200 to 2000.
+
2008-08-25 Andrew John Hughes <gnu_andrew@member.fsf.org>
* gnu/testlet/java/lang/Enum/PR33183.java:
Index: gnu/testlet/java/net/ServerSocket/AcceptTimeout.java
===================================================================
RCS file: /cvs/mauve/mauve/gnu/testlet/java/net/ServerSocket/AcceptTimeout.java,v
retrieving revision 1.1
diff -u -3 -p -r1.1 AcceptTimeout.java
--- gnu/testlet/java/net/ServerSocket/AcceptTimeout.java 14 May 2006 19:55:28 -0000 1.1
+++ gnu/testlet/java/net/ServerSocket/AcceptTimeout.java 1 Sep 2008 09:34:35 -0000
@@ -39,7 +39,7 @@ public class AcceptTimeout implements Te
try
{
ServerSocket ss = new ServerSocket(port);
- ss.setSoTimeout(200);
+ ss.setSoTimeout(2000);
Socket s = ss.accept();
harness.check(s.getSoTimeout(), 0);
s.close();
reply other threads:[~2008-09-01 9:39 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=1220261943.11930.3.camel@cthalinger \
--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).