| 72c9e00f7b2c4bd5574341f101ce72a372ffe40f |
|
19-Jan-2016 |
Narayan Kamath <narayan@google.com> |
Fix ConcurrentCloseTest#test_write.
NOTE: This was a bullhead specific failure.
Change-Id: Ic22e39aa4be17adc1959126b0fc6bfbf6176251f
|
| 271e9ada533970e09897bbde8858e991a07ba245 |
|
19-Mar-2013 |
Elliott Hughes <enh@google.com> |
Fix ConcurrentCloseTest's write test to ensure we're really blocked in write(2).
Bug: 8272932
Change-Id: Id0b9b23176bf179af85bcaf321df5bab05b093be
|
| 0e1afa1091f74a6228c01d8c7a8eebf001efdc57 |
|
13-Oct-2012 |
Elliott Hughes <enh@google.com> |
Fix ConcurrentCloseTest flakiness.
We can't rely on consuming all the listen(2) backlog. For the tests we've
seen fail because they sometimes connect rather than time out, switch to
an unroutable address.
(cherry-pick of babccbf9e429c4c78aca24c205825ceaaf7d3f37.)
Bug: 6971145
Change-Id: Ibfa412ff1ad7da7e63842d0162cc67a706e2b27e
|
| babccbf9e429c4c78aca24c205825ceaaf7d3f37 |
|
13-Oct-2012 |
Elliott Hughes <enh@google.com> |
Fix ConcurrentCloseTest flakiness.
We can't rely on consuming all the listen(2) backlog. For the tests we've
seen fail because they sometimes connect rather than time out, switch to
an unroutable address.
Bug: 6971145
Change-Id: I259d31b1a15123bcd78c36849d5ed863d392ac20
|
| 78601286edbfed7ea072814763f661eb80f6e777 |
|
10-Oct-2012 |
Elliott Hughes <enh@google.com> |
Extra log output for ConcurrentCloseTest flakiness.
No clue what's wrong here, but we're seeing some flakiness in the
"connect" tests. Hopefully there will be a clue in this extra
output next time we see a failure.
(cherry-pick of 735875881f3995ec6a687e65a2e5495304bc48be.)
Bug: 6971145
Change-Id: I8236b2fb368581e2b6965898f109370e7e0af2e5
|
| 735875881f3995ec6a687e65a2e5495304bc48be |
|
10-Oct-2012 |
Elliott Hughes <enh@google.com> |
Extra log output for ConcurrentCloseTest flakiness.
No clue what's wrong here, but we're seeing some flakiness in the
"connect" tests. Hopefully there will be a clue in this extra
output next time we see a failure.
Bug: 6971145
Change-Id: Ifed716cba5a17cab84e9535ec054785ee7d09aa7
|
| 3d43199950729e592ac3e104442b4b350a86aec8 |
|
26-Sep-2012 |
Elliott Hughes <enh@google.com> |
Fix ConcurrentCloseTest flakiness.
We were running the risk that the server's end of a client socket would get
closed by the finalizer thread, resulting in read(2) returning 0 to the client,
and the test failing like this:
junit.framework.AssertionFailedError: read returned -1
at libcore.java.net.ConcurrentCloseTest.test_read(ConcurrentCloseTest.java:121)
at java.lang.reflect.Method.invokeNative(Native Method)
(cherry-pick of 4bbcd7e5aee1e984a4fcf46385667f9ad03dbc16.)
Bug: 7206024
Change-Id: I0dae214a7ee609655f4f4781abf4457863bcfd5f
|
| 4bbcd7e5aee1e984a4fcf46385667f9ad03dbc16 |
|
26-Sep-2012 |
Elliott Hughes <enh@google.com> |
Fix ConcurrentCloseTest flakiness.
We were running the risk that the server's end of a client socket would get
closed by the finalizer thread, resulting in read(2) returning 0 to the client,
and the test failing like this:
junit.framework.AssertionFailedError: read returned -1
at libcore.java.net.ConcurrentCloseTest.test_read(ConcurrentCloseTest.java:121)
at java.lang.reflect.Method.invokeNative(Native Method)
Bug: 7206024
Change-Id: I3f228dc4d3bfb59f6595ebe255de2cf4047d06b8
|
| 796f0d5a4e7b83c3efc5e587b6766977dc20b0c3 |
|
16-Feb-2012 |
Elliott Hughes <enh@google.com> |
Fix asynchronous interruption of Socket.connect with a timeout.
Turns out there was one connect variant I hadn't properly addressed.
Bug: http://code.google.com/p/android/issues/detail?id=24318
Change-Id: I7af697bdf6ea17ad1f8ea904d7d8a051ffb970d2
|
| 5fc5dde4c719c1dfdac46b67d5d2e4884d07721e |
|
16-Nov-2010 |
Elliott Hughes <enh@google.com> |
Improve ConcurrentCloseTest.
No more flaky use of 10.* addresses.
Bug: 3044772
Change-Id: I5ca8dc431b50950efdc818efe73eb9aba76ea67f
|
| 3c6ca77845ce5f0e80c4dc49617601918023c1ed |
|
27-Sep-2010 |
Elliott Hughes <enh@google.com> |
Don't wrap select(2) in TEMP_FAILURE_RETRY.
Luckily, since the caller has to cope with us saying "we're not connected yet,
try again", we can just go that route.
I've also added another plausible possible exception to one of the tests, seen
once when testing on a host dalvikvm.
Bug: 3022824
Change-Id: Ia155f86f9f7b9b0a54e58c55f668faaebcbda55e
|
| 4557728efb66c455a52b7669a8eefef7a9e54854 |
|
11-Aug-2010 |
Jesse Wilson <jessewilson@google.com> |
Moving tests to be under the libcore.* package.
This is indended to make it easier to run on VMs that restrict the packages
from which application classes can be loaded. For example, on the RI you need
to use the bootclasspath to load these tests.
Change-Id: I52193f35c5fcca18b5a3e1d280505b1e29b388af
|