You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/05/03 12:32:16 UTC

[jira] [Resolved] (SLING-2818) ErrorHandlingTest often fails

     [ https://issues.apache.org/jira/browse/SLING-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-2818.
----------------------------------------

    Resolution: Fixed

The cause was an uploaded script changing the JSP engine config via an uploaded script before running the first JSP test. Depending on timing, the engine wasn't ready when the test executes.

I have moved the JSP engine config to initial content in http://svn.apache.org/r1478715 , so that it's configured at startup to avoid timing issues.
                
> ErrorHandlingTest often fails
> -----------------------------
>
>                 Key: SLING-2818
>                 URL: https://issues.apache.org/jira/browse/SLING-2818
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>         Attachments: error-message.txt
>
>
> At least at https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6 the org.apache.sling.launchpad.webapp.integrationtest.servlets.resolver.errorhandler.ErrorHandlingTest often fails, sometimes for unclear reasons (timing?).
> Recent error messages include
> At ErrorHandlingTest.setUp:
> mkdir(http://localhost:42232/apps/servlets/errorhandler) failed, status code=503
> At ErrorHandlingTest.test_500_errorhandling:
> Error 503 AuthenticationSupport service missing. Cannot authenticate request
> It looks like something (maybe the test's setup itself) causes Sling to go 503 just before the test.
> The test that runs just before is org.apache.sling.launchpad.webapp.integrationtest.CreateNodeTest which shouldn't cause a 503 status.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira