Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08F3317AA6 for ; Fri, 7 Nov 2014 17:54:34 +0000 (UTC) Received: (qmail 13096 invoked by uid 500); 7 Nov 2014 17:54:33 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 13054 invoked by uid 500); 7 Nov 2014 17:54:33 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 13044 invoked by uid 99); 7 Nov 2014 17:54:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Nov 2014 17:54:33 +0000 Date: Fri, 7 Nov 2014 17:54:33 +0000 (UTC) From: "lucas theisen (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DIRSERVER-2015) Build of xdbm fails when using java 8 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 lucas theisen created DIRSERVER-2015: ---------------------------------------- Summary: Build of xdbm fails when using java 8 Key: DIRSERVER-2015 URL: https://issues.apache.org/jira/browse/DIRSERVER-2015 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M18 Environment: Windows 7, Java 8 Reporter: lucas theisen When attempting to build using: {code} $ java -version java version "1.8.0_25" Java(TM) SE Runtime Environment (build 1.8.0_25-b18) Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode) {code} It fails with: {code} testAndCursorWithCursorBuilder(org.apache.directory.server.xdbm.search.impl= .AndCursorTest) Time elapsed: 0.034 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<...000-0000-00000000000[5]> but was:= <...000-0000-00000000000[8]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.directory.server.xdbm.search.impl.AndCursorTest.testA= ndCursorWithCursorBuilder(AndCursorTest.java:183) testAndCursorWithManualFilter(org.apache.directory.server.xdbm.search.impl.= AndCursorTest) Time elapsed: 0.004 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<...000-0000-00000000000[5]> but was:= <...000-0000-00000000000[8]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.directory.server.xdbm.search.impl.AndCursorTest.testA= ndCursorWithManualFilter(AndCursorTest.java:218) {code} Discussion on this issue over irc: {quote} \[11:07] xdbm unit tests fail on windows \[11:08] testNestedAndnOr(org.apache.directory.server.xdbm.s= earch.impl.NestedFilterTest) Time elapsed: 0.004 sec <<< FAILURE! org.jun= it.ComparisonFailure: expected:<...000-0000-00000000000\[5]> but was:<...00= 0-0000-00000000000\[9]> at org.junit.Assert.assertEquals(Assert.jav= a:115) at org.junit.Assert.assertEquals(Assert.java:144) at= org.apache.directory.server.xdbm.search.impl.NestedFilterTest.testNestedAn= dnOr(NestedFilterTest.java:193) \[11:28] hmmm \[11:30] same failure for me :/ \[11:35] i dont know what xdbm is... \[11:35] lucastheisen: that's extratordinary, it fails when run= in eclipse, not when I run the tests in the CL \[11:36] mine failed on CL, though i run from cygwin, so tha= t could add more fuzziness to the mix \[11:36] Running org.apache.directory.server.xdbm.search.impl.N= estedFilterTest \[11:36] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time= elapsed: 0.217 sec - in org.apache.directory.server.xdbm.search.impl.Neste= dFilterTest \[11:37] what Java version are you using ? \[11:37] mine is 1.7.0_55 \[11:38] ltheisen@MM206678-PC ~/svn/apacheds-trunk-with-depe= ndencies/apacheds $ java -version java version "1.8.0_25" Java(TM) SE Runti= me Environment (build 1.8.0_25-b18) Java HotSpot(TM) 64-Bit Server VM (buil= d 25.25-b02, mixed mode) \[11:50] this is another fucking JVM issue \[11:50] when I run the test with 1.7, it passes \[11:50] when I switch to 1.8, it fails \[11:50] now to understand why... \[11:54] dam. \[11:55] there is another issue : the candidate count seems wro= ng \[11:55] (|:\[5](&:\[3](cn=3Dj*:\[3])(sn=3Dw*:\[=E2=88=9E]))(ou= =3Dapache:\[2])) \[11:55] should be \[11:55] (|:\[5](&:\[3](cn=3Dj*:\[6])(sn=3Dw*:\[=E2=88=9E]))(ou= =3Dapache:\[2])) \[11:57] ah, no \[12:04] damn it=E2=80=A6 \[12:04] I see at least 2 problems here \[12:04] - the count for cn=3Dj* is wrong, it should be 6 \[12:05] - there is most certainly an issue with some internal = java class we use to store the candidates, it has probably changed between = Java 7 and Java 8 \[12:05] so you get the entries in a different order \[12:06] that requires some investigation \[12:06] I don't think the API is in cause here, it's really an= ApacheDS issue {quote} -- This message was sent by Atlassian JIRA (v6.3.4#6332)