Fix method order in order to make the execution of TestEntryLog predictable
### Motivation
TestEntyLog reuses the entryLogger variable across test methods execution, resulting in an unpredictable execution.
We can at least make the test work consistently across environments using JUnit built-in FixMethodOrder annotation
### Changes
FixMethodOrder(MethodSorters.NAME_ASCENDING)
Fixes #2260
Reviewers: Atri Sharma <atri@apache.org>
This closes #2266 from eolivelli/fix/flaky
diff --git a/bookkeeper-server/src/test/java/org/apache/bookkeeper/bookie/TestEntryLog.java b/bookkeeper-server/src/test/java/org/apache/bookkeeper/bookie/TestEntryLog.java
index 836fdf2..fd35204 100644
--- a/bookkeeper-server/src/test/java/org/apache/bookkeeper/bookie/TestEntryLog.java
+++ b/bookkeeper-server/src/test/java/org/apache/bookkeeper/bookie/TestEntryLog.java
@@ -67,13 +67,16 @@
import org.junit.After;
import org.junit.Assert;
import org.junit.Before;
+import org.junit.FixMethodOrder;
import org.junit.Test;
+import org.junit.runners.MethodSorters;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
/**
* Tests for EntryLog.
*/
+@FixMethodOrder(MethodSorters.NAME_ASCENDING)
public class TestEntryLog {
private static final Logger LOG = LoggerFactory.getLogger(TestEntryLog.class);