https://bz.apache.org/bugzilla/show_bug.cgi?id=61393
Bug ID: 61393
Summary: org.apache.tomcat.jni.TestSocketServer timeout failure
on a fast computer
Product: Tomcat 9
Version: 9.0.0.M25
Hardware: PC
Status: NEW
Severity: minor
Priority: P2
Component: Connectors
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: -----
Testing 9.0.0.M26 release candidate on a fast PC,
on Windows 10 with Tomcat Native dll in bin/native/.
I see the following failure in
TEST-org.apache.tomcat.jni.TestSocketServer.APR.txt
(The same result for NIO, NIO2 connectors as well, as this is a jni test -
regardless of connector).
[[[
Testcase: testBlockingReadFromClientWithTimeout took 1,015 sec
FAILED
Socket.timeoutSet failed (<1s) [985435824]
junit.framework.AssertionFailedError: Socket.timeoutSet failed (<1s)
[985435824]
at
org.apache.tomcat.jni.TestSocketServer.testBlockingReadFromClientWithTimeout(TestSocketServer.java:99)
]]]
The value [985435824] is marginally smaller than expected 1000000000.
I wonder whether timeout is calculated from some earlier moment (that is - move
"long start = System.nanoTime();" line earlier), or some arithmetic error is
allowed here (introduce an error margin).
All other tests completed successfully.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]