[
https://issues.apache.org/jira/browse/SLING-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-257.
---------------------------------------
Resolution: Fixed
Increasing the timeout to 60 seconds (rev 629042) solves the problem in my
environment, the drag is that tests will now wait that much before aborting, if
the required Sling services are really not ready.
> Launchpad integration tests sometimes fail in slow environments
> ---------------------------------------------------------------
>
> Key: SLING-257
> URL: https://issues.apache.org/jira/browse/SLING-257
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Reporter: Bertrand Delacretaz
>
> When doing a full Sling build with "mvn clean install" from the top of the
> sling code tree on my laptop, the Launchpad integration tests often fail,
> with messages such as:
> java.io.IOException: Expected status code 302 for POST, got 404,
> URL=http://localhost:8888/org.apache.sling.launchpad.webapp-2.0.0-incubator-SNAPSHOT/WaitForSlingStartup_1203410589689
> in the surefire-reports files.
> I think I've seen this on http://vmbuild.apache.org/continuum/ as well.
> Looking at the logs, it seems like this is due to a too short timeout in the
> launchpad HttpTestBase.waitForSlingStartup().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
