Colin/Ahmed,
Can you run with debug logging turned on and attach the logs? You could
just change log level in clients/src/test/resources/log4j.properties and
run the tests.
Thanks,
Rajini
On Tue, Jun 26, 2018 at 7:40 PM, Colin McCabe wrote:
> On trunk, testMultipleServerMechanisms failed
On trunk, testMultipleServerMechanisms failed for me, as well as
testAuthenticateCallbackHandlerMechanisms and testMechanismPluggability.
org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest >
testMultipleServerMechanisms FAILED
java.lang.AssertionError
at
I ran the test on Linux as well.
cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /jdk1.8.0_161/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-327.28.3.el7.x86_64", arch: "amd64",
Here was the command I used:
./gradlew -Dtest.single=SaslAuthenticatorTest clients:test
On Mon, Jun 25, 2018 at 5:39 PM, Ahmed A wrote:
> I ran test with -i option as follows - "./gradlew -i test". The same set
> of three tests failed.
>
> My environment:
> $ java -version
> java version
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
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:
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
