My machine is "fast" but it is often "busy". Is there a way to make the test more deterministic?
Gary On Mon, May 26, 2014 at 11:55 AM, Remko Popma <[email protected]> wrote: > It seems that this test frequently fails spuriously on slow or busy > machines. > I will remove the test. > > > On Mon, May 26, 2014 at 11:05 PM, Gary Gregory <[email protected]>wrote: > >> With the latest from trunk, I get this error: >> >> Failed tests: >> CachedClockTest.testLessThan17Millis:32 diff too large: 75 >> >> Tests run: 630, Failures: 1, Errors: 0, Skipped: 28 >> >> Gary >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second >> Edition<http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> > > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
