I ran test with -i option as follows - "./gradlew -i test". The same set of three tests failed.
My environment: $ java -version java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) $ cat /etc/redhat-release Red Hat Enterprise Linux Workstation release 7.3 (Maipo) $ uname -a Linux ahmed 3.10.0-514.36.5.el7.x86_64 #1 SMP Thu Dec 28 21:42:18 EST 2017 x86_64 x86_64 x86_64 GNU/Linux Can you please let me know how I can run an individual unit test, what options do I provide? Thank you, Ahmed. On Mon, Jun 25, 2018 at 2:47 PM, Ted Yu <yuzhih...@gmail.com> wrote: > I ran the test alone which passed. > > Can you include -i on the command line to see if there is some clue from > the output ? > > Here is my environment: > > Java version: 1.8.0_151, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_151.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac" > > FYI > > On Mon, Jun 25, 2018 at 12:59 PM, Ahmed A <ahmeda5...@gmail.com> wrote: > > > Hello, > > > > I did a fresh clone of the kafka src code, and the following SASL unit > > tests have been failing consistently: > > - testMechanismPluggability > > - testMechanismPluggability > > - testMultipleServerMechanisms > > > > All three tests have similar stack trace: > > at org.junit.Assert.assertTrue(Assert.java:52) > > at > > org.apache.kafka.common.network.NetworkTestUtils.waitForChannelReady( > > NetworkTestUtils.java:79) > > at > > org.apache.kafka.common.network.NetworkTestUtils.checkClientConnection( > > NetworkTestUtils.java:52) > > > > I also noticed, the three tests are using digest-md5. > > > > Has anyone else run into a similar issue or have any ideas for the > failure? > > > > Thank you, > > Ahmed. > > >
