Yes, the error messages look very much related to https://issues.apache.org/jira/browse/SLING-2251
expected:<[http://localhost:38340]/VanityPathTest_1323...> but was:<[]/VanityPathTest_1323...> expected:<[http://localhost:38340]/VanityPathTest_1323...> but was:<[]/VanityPathTest_1323...> expected:<[http://localhost:38340]/VanityPathTest_1323...> but was:<[]/VanityPathTest_1323...> The integration tests need to be adapted. Ideally, they properly resolve any relative URL to an absolute one first (using a base URL) and check against that one. Cheers, Alex On 12.12.11 20:46, "Jeff Young" <[email protected]> wrote: >Felix recently committed a change by Alex relating to the: > org.apache.sling.servlets.get.impl.RedirectServletTest >no longer returning absolute paths. > >It would appear that the failing tests are the same issue, but from: > org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest. > >Cheers, >Jeff. > > >-----Original Message----- >From: Apache Jenkins Server [mailto:[email protected]] >Sent: 12 December 2011 19:11 >To: [email protected] >Subject: Jenkins build is still unstable: sling-trunk-1.5 » Apache Sling >Launchpad Testing WAR version #1479 > >See ><https://builds.apache.org/job/sling-trunk-1.5/org.apache.sling$org.apache >.sling.launchpad.testing-war/1479/> > > > -- Alexander Klimetschek Developer // Adobe (Day) // Berlin - Basel
