Hi Guys, I'm referring to http://svn.apache.org/repos/asf/directory/apacheds/trunk-with-dependencies with no mods whatsoever (I planned to get a stable base and then submit some of the "more likely to interest you guys" patches for review). Unfortunately I "mvn clean"ed and moved my ~/.m2/repository out of the way and rebuilt and can confirm I see the same failures.
Don't know enough about the new build / code to comment with much authority but it doesn't seem to me that the core-integ failures are knock-on effects from the jdbm-store failures. Thanks On Mon, Sep 8, 2008 at 3:40 PM, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > The best would be to erase the .m2/repository, do a complete svn co of > the code, run mvn and see what happens. A litle bit long, but the > best way to avoid any usage of any old jars... > > Oh, and do that in a clean directory on your disk. And don't forget to > curse Widnows twice ;) > > On Mon, Sep 8, 2008 at 6:19 AM, Alex Karasulu <[EMAIL PROTECTED]> wrote: >> Are you able to build the stock trunk without any of your modifications? I >> just want to confirm your environment works for the basis case. >> >> Alex >> >> On Sun, Sep 7, 2008 at 8:39 PM, Norval Hope <[EMAIL PROTECTED]> wrote: >>> >>> Couldn't see in the various pom.xmls where the "system" and "schema" >>> directories were named as such, but did this >>> >>> cp -r apaches/core/target/server_work/schema >>> apaches/core/target/server_work/system >>> >>> and retried "mvn install" in apacheds/core-integ/ but unfortunately >>> got the same bulk failures (or more exactly errors) so have attached >>> both the text output by "mvn install" and the surefire results: >>> >>> Tests run: 381, Failures: 0, Errors: 188, Skipped: 0 >>> >>> I'm afraid I don't have enough of a feel for the more recent 1.5 build >>> / code to make sense of this but my gut feeling is that root problems >>> may be down to: >>> 1) the system/ versus schema/ name >>> 2) differences in Windows file system semantics (notice complaints >>> about not being able to delete the server-work/ directory) which might >>> be due to running processes still accessing files. >>> >>> Note I'm running Windows XP and JDK 1.5_011. >>> >>> Thanks >>> >>> >>> >>> On Mon, Sep 8, 2008 at 10:16 AM, Norval Hope <[EMAIL PROTECTED]> wrote: >>> > Also should report that when I moved the JdbmIndexTest out of the way >>> > and attempted to rebuild I got bulk failures as bellow: >>> > >>> > [INFO] [surefire:test] >>> > [INFO] Surefire report directory: >>> > C:\src\ad-1.5\apacheds\core-integ\target\surefire-reports >>> > >>> > ------------------------------------------------------- >>> > T E S T S >>> > ------------------------------------------------------- >>> > Running org.apache.directory.server.core.jndi.SearchWithIndicesITest >>> > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.078 >>> > sec >>> > Running org.apache.directory.server.core.suites.AuthzISuite >>> > Tests run: 48, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.094 >>> > sec >>> > Running org.apache.directory.server.core.suites.StockCoreISuite >>> > [10:06:02] ERROR >>> > [org.apache.directory.server.core.integ.IntegrationUtils] - Failed to >>> > delete the working directory. >>> > java.io.IOException: Unable to delete file: >>> > server-work\system\apacheSublevel.lg >>> > >>> > at >>> > org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1247) >>> > at >>> > org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:903) >>> > at >>> > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:869) >>> > at >>> > org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1239) >>> > at >>> > org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:903) >>> > at >>> > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:869) >>> > at >>> > org.apache.directory.server.core.integ.IntegrationUtils.doDelete(Inte >>> > grationUtils.java:73) >>> > at >>> > org.apache.directory.server.core.integ.state.StartedNormalState.clean >>> > up(StartedNormalState.java:85) >>> > at >>> > org.apache.directory.server.core.integ.state.TestServiceContext.clean >>> > up(TestServiceContext.java:147) >>> > at >>> > org.apache.directory.server.core.integ.CiSuite.run(CiSuite.java:120) >>> > at >>> > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. >>> > >>> > which seems to be a broken dependency perhaps as I find only this dir >>> > when I do a search from the root ad-1.5 directory: >>> > >>> > $ find . -name server-work >>> > ./apacheds/core/target/server-work >>> > >>> > and that directory has only a subdirectory schema/ rather then system/ >>> > , although this dir seems to have the file for which a delete was >>> > attempted. I'll try and see where that working directory name comes >>> > from and see what happens if I change "system" to "schema". >>> > >>> > On Mon, Sep 8, 2008 at 9:49 AM, Norval Hope <[EMAIL PROTECTED]> wrote: >>> >> Apologies - figured if the failed tests aren't specific to my env then >>> >> they probably signified something that needed to be fixed before a >>> >> release (but next time will just post to the dev list). >>> >> >>> >> The two tests that failed were: >>> >> >>> >> Tests in error: >>> >> >>> >> >>> >> testNoEqualityMatching(org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmIndexTest) >>> >> >>> >> >>> >> testSingleValuedAttribute(org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmIndexTest) >>> >> >>> >> which were the same two that were failing for me prior to your latest >>> >> commits. >>> >> >>> >> Thanks >>> >> >>> >> On Mon, Sep 8, 2008 at 8:58 AM, Alex Karasulu <[EMAIL PROTECTED]> >>> >> wrote: >>> >>> Which specific test failed and please don't use the vote thread for >>> >>> side >>> >>> conversations. >>> >>> >>> >>> Alex >>> >>> >>> >>> On Sun, Sep 7, 2008 at 6:55 PM, Norval Hope <[EMAIL PROTECTED]> wrote: >>> >>>> >>> >>>> Hi, >>> >>>> >>> >>>> I just updated and tried to rebuild but got the same failures. Is >>> >>>> this >>> >>>> a problem with my env only? >>> >>>> >>> >>>> Thanks >>> >>>> >>> >>>> On Mon, Sep 8, 2008 at 8:33 AM, Alex Karasulu <[EMAIL PROTECTED]> >>> >>>> wrote: >>> >>>> > Hi all, >>> >>>> > >>> >>>> > I've cleared the list of JIRA issues for 1.5.4. Time for the >>> >>>> > release. >>> >>>> > >>> >>>> > [ ] +1 release ApacheDS 1.5.4 >>> >>>> > [ ] +/- 0 abstain >>> >>>> > [ ] -1 do not release ApacheDS 1.5.4 >>> >>>> > >>> >>>> > -------- >>> >>>> > Issues - http://iefohm.notlong.com/ >>> >>>> > >>> >>>> > >>> >>>> > Alex >>> >>>> > >>> >>> >>> >>> >>> >> >>> > >> >> > > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com >
