Fix timeouts
GoogleCodeExporter opened this issue · comments
Timeouts are implemented in both host and target processes, with various
problems on each
side. We should do timeouts on the target process exclusively, because it has
more information
and can make a better decision. It can also do nice quality-of-service things
like calling
getStackTrace() on the blocked thread to diagnose what was taking so long.
To help check this feature, here's a test that times out reliably:
org.apache.harmony.archive.tests.java.util.zip.GZIPOutputStreamTest#testFlush
Original issue reported on code.google.com by jessewil...@google.com
on 27 Apr 2010 at 2:44
Original comment by jessewil...@google.com
on 6 May 2010 at 8:32
Fixed.
Original comment by jessewil...@google.com
on 19 May 2010 at 10:31
- Changed state: Fixed