Thanks, Roger. This is a much better test now (but still not actually a good one...)
Probably want to be optimistic and delete + * @key intermittent On Tue, May 19, 2015 at 6:50 PM, Roger Riggs <[email protected]> wrote: > Hi, > > Ok, how about this: > > Webrev: > http://cr.openjdk.java.net/~rriggs/webrev-lots-8078582/ > > Thanks, Roger > > > > On 5/19/15 7:55 PM, Martin Buchholz wrote: > > LotsOfOutput is a lousy test. totalMemory can grow with any quantum. > Better would be watching > usedMemory = Runtime.getRuntime().totalMemory() - > Runtime.getRuntime().freeMemory(); > as suggested at > > http://stackoverflow.com/questions/3571203/what-is-the-exact-meaning-of-runtime-getruntime-totalmemory-and-freememory > > On Tue, May 19, 2015 at 2:32 PM, Roger Riggs <[email protected]> > wrote: > >> Please review this update to a test to make it resilient to small >> allocations >> that may bump the total memory. The test will also collect more data if >> it fails again. >> >> Webrev: >> http://cr.openjdk.java.net/~rriggs/webrev-xx/ >> >> Issue: >> https://bugs.openjdk.java.net/browse/JDK-8078582 >> >> Thanks, Roger >> >> >> >> > >
