OK. I think I see the problem now. Logged as SLING-2292. I'll commit a fix you can try shortly.
On Thu, Nov 17, 2011 at 12:25 PM, Pontus Amberg <[email protected]> wrote: > I had no problem building Sling and I did not try to login using > OpenId. I just tried to access the root of the deployed WAR and > that shouldn't need any login, or? > > /Pontus > > On 2011-11-17 17:30, Justin Edelson wrote: >> >> On Thu, Nov 17, 2011 at 8:07 AM, Bertrand Delacretaz >> <[email protected]> wrote: >>> >>> On Thu, Nov 17, 2011 at 4:53 PM, Justin Edelson >>> <[email protected]> wrote: >>>> >>>> ...The failures in build 1438 were in the sample integration >>>> tests, which I've sadly learned to ignore... >>> >>> Those look good now, from the console output [1]: >>> >>> [INFO] Apache Sling Sample Integration Tests ............. SUCCESS >>> [1:16.140s] >>> [INFO] Apache Sling Launchpad Testing Services ........... SUCCESS >>> [14.357s] >>> [INFO] Apache Sling Launchpad Testing Services WAR ....... SUCCESS >>> [10.562s] >>> [INFO] Apache Sling Launchpad Test Bundles ............... SUCCESS >>> [10.661s] >>> [INFO] Apache Sling Integration Tests .................... SUCCESS >>> [19.372s] >>> [INFO] Apache Sling Launchpad Testing .................... SUCCESS >>> [6:18.637s] >>> [INFO] Apache Sling Launchpad Testing WAR version ........ FAILURE >>> [0.200s] >>> >>>> What I may not have done was run the war integration tests. I'd >>>> doublecheck those now. >>> >>> The above shows that those fail, on Jenkins at least. >>> >>> -Bertrand >>> >>> >>> [1]https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.5/1444/console >>> >> These tests pass locally for me, but I can see from the Jenkins log >> that there is a bug in the code introduced in SLING-2273. >> >> I do not believe that would cause the error Pontus reported as it is >> just a problem in calculating the dependencies of the testing-war >> project. >> >> Pontus - are you actually using OpenID? >> >> Justin >> > > >
