Hopefully add better timeouts and ordering to JDBCExtractionNamespaceTest #1658

drcrallen · 2015-08-22T02:38:11Z

I'll be opening and closing this a few times to see if I can get a failure case for JDBCExtractionNamespaceTest

xvrl · 2015-08-25T21:31:51Z

...espace-lookup/src/test/java/io/druid/server/namespace/cache/JDBCExtractionNamespaceTest.java

    );
+    committed.await(10, TimeUnit.SECONDS);
+    Thread.sleep(2);


any reason for the sleep here, given that we wait just before?

If latch completes within 1 ms it makes sure a few ms have elapsed. This is to help make sure things which only check on granularity of ms have a few ms spacing to acknowledge timestamp changes..

Added comments

drcrallen · 2015-08-26T07:00:08Z

Failure in SQLMetadataStorageActionHandlerTest.testLocks:227 » CallbackFailed org.skife.j. restarting

drcrallen · 2015-08-26T14:22:13Z

testDelete(io.druid.server.namespace.cache.NamespaceExtractionCacheManagerExecutorsTest)  Time elapsed: 50.009 sec  <<< ERROR!
java.lang.Exception: test timed out after 50000 milliseconds
    at io.druid.server.namespace.cache.NamespaceExtractionCacheManager.removeNamespaceLocalMetadata(NamespaceExtractionCacheManager.java:296)
    at io.druid.server.namespace.cache.NamespaceExtractionCacheManager.delete(NamespaceExtractionCacheManager.java:514)
    at io.druid.server.namespace.cache.OnHeapNamespaceExtractionCacheManager.delete(OnHeapNamespaceExtractionCacheManager.java:99)
    at io.druid.server.namespace.cache.NamespaceExtractionCacheManagerExecutorsTest.testDelete(NamespaceExtractionCacheManagerExecutorsTest.java:333)
    at io.druid.server.namespace.cache.NamespaceExtractionCacheManagerExecutorsTest.testDelete(NamespaceExtractionCacheManagerExecutorsTest.java:258)
Running io.druid.server.namespace.URIExtractionNamespaceFunctionFactoryTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.641 sec - in io.druid.server.namespace.URIExtractionNamespaceFunctionFactoryTest
Results :
Tests in error: 
  NamespaceExtractionCacheManagerExecutorsTest.testDelete:258->testDelete:333 »

Failure in another test, restarting to see if I can get a JDBC test failure

drcrallen · 2015-08-26T16:30:24Z

failed on WorkerTaskMonitorTest.testGetAnnouncements:222 null

…Test

drcrallen · 2015-09-01T23:46:06Z

This seems to be in a pretty good state overall.

xvrl · 2015-09-02T18:15:56Z

👍

nishantmonu51 · 2015-09-02T18:19:45Z

+1

Hopefully add better timeouts and ordering to JDBCExtractionNamespaceTest

drcrallen closed this Aug 25, 2015

drcrallen reopened this Aug 25, 2015

drcrallen closed this Aug 25, 2015

drcrallen reopened this Aug 25, 2015

drcrallen force-pushed the cleanupJDBCExtractionNamespaceTest branch from ec50205 to 9a34c54 Compare August 25, 2015 05:06

drcrallen closed this Aug 25, 2015

drcrallen reopened this Aug 25, 2015

drcrallen closed this Aug 25, 2015

drcrallen reopened this Aug 25, 2015

drcrallen closed this Aug 25, 2015

drcrallen reopened this Aug 25, 2015

drcrallen force-pushed the cleanupJDBCExtractionNamespaceTest branch 2 times, most recently from 8117664 to a063a72 Compare August 25, 2015 18:22

drcrallen closed this Aug 25, 2015

drcrallen reopened this Aug 25, 2015

drcrallen closed this Aug 25, 2015

drcrallen reopened this Aug 25, 2015

drcrallen force-pushed the cleanupJDBCExtractionNamespaceTest branch from a063a72 to 299c5bc Compare August 25, 2015 19:40

xvrl reviewed Aug 25, 2015
View reviewed changes

drcrallen force-pushed the cleanupJDBCExtractionNamespaceTest branch 3 times, most recently from 3c41b27 to 1555763 Compare August 25, 2015 23:38

drcrallen closed this Aug 26, 2015