killbill-memoizeit

beatrix: be even more generous with the globalLock timeout Signed-off-by:

10/17/2018 11:51:31 AM

Details

diff --git a/beatrix/src/test/java/org/killbill/billing/beatrix/BeatrixTestSuiteWithEmbeddedDB.java b/beatrix/src/test/java/org/killbill/billing/beatrix/BeatrixTestSuiteWithEmbeddedDB.java
index bf8f01f..53506d1 100644
--- a/beatrix/src/test/java/org/killbill/billing/beatrix/BeatrixTestSuiteWithEmbeddedDB.java
+++ b/beatrix/src/test/java/org/killbill/billing/beatrix/BeatrixTestSuiteWithEmbeddedDB.java
@@ -36,7 +36,7 @@ public abstract class BeatrixTestSuiteWithEmbeddedDB extends GuicyKillbillTestSu
                                                                                                                   // in the listener status: after moving the clock, if there are two notifications triggering an invoice run, we typically expect
                                                                                                                   // both an INVOICE and a NULL_INVOICE event. If the invoice generation takes too long, the NULL_INVOICE event is never generated
                                                                                                                   // (LockFailedException): the test itself doesn't fail (the correct invoice is generated), but assertListenerStatus() would.
-                                                                                                                  .put("org.killbill.invoice.globalLock.retries", "150")
+                                                                                                                  .put("org.killbill.invoice.globalLock.retries", "300")
                                                                                                                   .build();
 
     @Override