[
https://issues.apache.org/jira/browse/SLING-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-3235.
----------------------------------------
Resolution: Fixed
Should be fixed by http://svn.apache.org/r1542223
The test-services bundle now includes configs which are installed
asynchronously at startup and cause Sling to temporarily respond with 503. The
tests now check URLs that (hopefully) indicate when a stable state is reached.
> 503 error at the beginning of integration tests
> -----------------------------------------------
>
> Key: SLING-3235
> URL: https://issues.apache.org/jira/browse/SLING-3235
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> Our launchpad/testing tests sometimes seem to start before Sling is actually
> ready, see example below.
> Sling services seem to be started, continuing with integration tests.
> ...
> StreamServletTest.testHtmlFile(ERROR!
> org.apache.sling.commons.testing.integration.HttpStatusCodeException:
> Expected status code 200 for GET, got 503...
> testPlainTextFile <<< ERROR!
> java.io.IOException: mkdir(
> http://localhost:60527/launchpad-integration-tests) failed, status code=503
> Running org.apache.sling.launchpad.webapp.integrationtest.EspLoadTest
> <<< ERROR!
> org.apache.sling.commons.testing.integration.HttpStatusCodeException:
> Expected status code 302 for POST, got 503,
> URL=http://localhost:60527/EspLoadTest_1383722876765/, Content=[<html>
> <head>
> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
> <title>Error 503 ServletResolver service missing, cannot service
> requests</title>
> ...and the following tests pass
--
This message was sent by Atlassian JIRA
(v6.1#6144)
