Re: Non-flaky test failures

I filed GEODE-1568 and disabled PreloadedRegionTestCase from being run as a dunit test. -Kirk On Sat, Jun 18, 2016 at 6:17 PM, Kirk Lund wrote: > I took a closer look at PreloadedRegionTestCase... > > PreloadedRegionTestCase was only recently "enabled" to run as a test by >

Re: Non-flaky test failures

I took a closer look at PreloadedRegionTestCase... PreloadedRegionTestCase was only recently "enabled" to run as a test by the fix for GEODE-1374 (gradle changes for FlakyTests) and the fix for GEODE-837 (upgrading all dunit tests to JUnit4). Prior to that commit, it was not being executed as a

Re: Non-flaky test failures

Looks like I may be responsible for breaking CommandOverHttpDUnitTest :( I'll fix this one as soon as possible (probably tomorrow morning). Sorry! -Kirk On Friday, June 17, 2016, Kirk Lund wrote: > CommandOverHttpDUnitTest is new and runs GFSH commands over HTTP. I think >

Re: Non-flaky test failures

CommandOverHttpDUnitTest is new and runs GFSH commands over HTTP. I think we need to mark that whole class with FlakyTest for now. The tests using runRepeatingIfNecessary are prone to timing issues which *may* have been impacted by me removing the retry loop in VM invoke. That removal was correct

Non-flaky test failures

The most recent jenkins run [1] had 3 failures from non-flaky tests. The geode-core tests seem to reproduce pretty easily. Have there been any recent changes in this area? :geode-core:distributedTest com.gemstone.gemfire.cache30. PreloadedRegionTestCase > testTXNonblockingGetInitialImage