My full-reactor build failure problem is back and it seems to be related to the state of the sling directory in the root of the source tree.
$ rm -rf sling $ mvn clean install consistently works but $ mvn clean install $ mvn clean install consistently fails. This should be reasonably simple to resolve by adding an execution of the clean plugin to the root pom. The node in ContentLoaderMiscPropertyTest is created by the content loader. See launchpad/test-services/src/main/resources/SLING-INF/content/property-types-test.json Which assertion is failing for you? Justin On 9/9/10 10:05 AM, Felix Meschberger wrote: > Hi, > > Addendum: I am running on Linux with either Java 5 or Java 6. > > Also: The ContentLoaderMiscPropertyTest test on a virgin Sling instance > (e.g. by running as a JUnit test from within Eclipse) will always fail. > So I suspect the test to expect some left-over file from another test. > > Regards > Felix > > On 09.09.2010 15:55, Justin Edelson wrote: >> I _was_ seeing this until about a week ago, but it was slightly >> different... a full reactor build would fail, but mvn clean install in >> launchpad/testing would always pass. >> >> Since about a week ago (sorry, don't know the revision), both have >> passed pretty consistently. >> >> Running a build now... >> >> Justin >> >> On 9/9/10 8:53 AM, Felix Meschberger wrote: >>> Hi all, >>> >>> Maybe its just me, but currently the Sling (main) integration tests run >>> extremely unstable. Most of the time I only have one failure. But 1 out >>> of 4 runs, I have a random (but rather high) number of test failures. >>> >>> I run "mvn -o clean install" in the launchpad/testing folder after a >>> full reactor build. >>> >>> The single test that constantly fails is >>> ContentLoaderMiscPropertyTest.testLoaded. This expects a node, which I >>> cannot find where it is created. >>> >>> Do you observe the same ? >>> >>> Thanks and Regards >>> Felix >> >>
