You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Ahmed A <ah...@gmail.com> on 2018/06/25 19:59:06 UTC
SASL Unit test failing
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.
Re: SASL Unit test failing
Posted by Rajini Sivaram <ra...@gmail.com>.
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 <cm...@apache.org> wrote:
> 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 org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> 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)
> at org.apache.kafka.common.security.authenticator.
> SaslAuthenticatorTest.testMultipleServerMechanisms(
> SaslAuthenticatorTest.java:281)
>
> org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest >
> testAuthenticateCallbackHandlerMechanisms FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> 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)
> at org.apache.kafka.common.security.authenticator.
> SaslAuthenticatorTest.createAndCheckClientConnection
> (SaslAuthenticatorTest.java:1475)
> at org.apache.kafka.common.security.authenticator.
> SaslAuthenticatorTest.testAuthenticateCallbackHandlerMechanisms(
> SaslAuthenticatorTest.java:776)
>
> org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest >
> testMechanismPluggability FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> 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)
> at org.apache.kafka.common.security.authenticator.
> SaslAuthenticatorTest.createAndCheckClientConnection
> (SaslAuthenticatorTest.java:1475)
> at org.apache.kafka.common.security.authenticator.
> SaslAuthenticatorTest.testMechanismPluggability(
> SaslAuthenticatorTest.java:257)
>
> best,
> Colin
>
> On Mon, Jun 25, 2018, at 18:02, Ted Yu wrote:
> > 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",
> > family: "unix"
> >
> > On Mon, Jun 25, 2018 at 5:42 PM, Ted Yu <yu...@gmail.com> wrote:
> >
> > > Here was the command I used:
> > >
> > > ./gradlew -Dtest.single=SaslAuthenticatorTest clients:test
> > >
> > > On Mon, Jun 25, 2018 at 5:39 PM, Ahmed A <ah...@gmail.com> 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 "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 <yu...@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 <ah...@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.checkClient
> > >> Connection(
> > >> > > 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.
> > >> > >
> > >> >
> > >>
> > >
> > >
>
Re: SASL Unit test failing
Posted by Colin McCabe <cm...@apache.org>.
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 org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
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)
at org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testMultipleServerMechanisms(SaslAuthenticatorTest.java:281)
org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest > testAuthenticateCallbackHandlerMechanisms FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
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)
at org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.createAndCheckClientConnection(SaslAuthenticatorTest.java:1475)
at org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testAuthenticateCallbackHandlerMechanisms(SaslAuthenticatorTest.java:776)
org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest > testMechanismPluggability FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
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)
at org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.createAndCheckClientConnection(SaslAuthenticatorTest.java:1475)
at org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testMechanismPluggability(SaslAuthenticatorTest.java:257)
best,
Colin
On Mon, Jun 25, 2018, at 18:02, Ted Yu wrote:
> 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",
> family: "unix"
>
> On Mon, Jun 25, 2018 at 5:42 PM, Ted Yu <yu...@gmail.com> wrote:
>
> > Here was the command I used:
> >
> > ./gradlew -Dtest.single=SaslAuthenticatorTest clients:test
> >
> > On Mon, Jun 25, 2018 at 5:39 PM, Ahmed A <ah...@gmail.com> 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 "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 <yu...@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 <ah...@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.checkClient
> >> Connection(
> >> > > 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.
> >> > >
> >> >
> >>
> >
> >
Re: SASL Unit test failing
Posted by Ted Yu <yu...@gmail.com>.
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",
family: "unix"
On Mon, Jun 25, 2018 at 5:42 PM, Ted Yu <yu...@gmail.com> wrote:
> Here was the command I used:
>
> ./gradlew -Dtest.single=SaslAuthenticatorTest clients:test
>
> On Mon, Jun 25, 2018 at 5:39 PM, Ahmed A <ah...@gmail.com> 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 "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 <yu...@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 <ah...@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.checkClient
>> Connection(
>> > > 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.
>> > >
>> >
>>
>
>
Re: SASL Unit test failing
Posted by Ted Yu <yu...@gmail.com>.
Here was the command I used:
./gradlew -Dtest.single=SaslAuthenticatorTest clients:test
On Mon, Jun 25, 2018 at 5:39 PM, Ahmed A <ah...@gmail.com> 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 "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 <yu...@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 <ah...@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.
> > >
> >
>
Re: SASL Unit test failing
Posted by Ahmed A <ah...@gmail.com>.
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 <yu...@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 <ah...@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.
> >
>
Re: SASL Unit test failing
Posted by Ted Yu <yu...@gmail.com>.
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 <ah...@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.
>