Robert Munteanu created SLING-2959:
--------------------------------------
Summary: ErrorHandlingTest intermitent failures in setUp
Key: SLING-2959
URL: https://issues.apache.org/jira/browse/SLING-2959
Project: Sling
Issue Type: Bug
Components: Testing
Reporter: Robert Munteanu
Assignee: Robert Munteanu
I believe that these failures happen because the tearDown method deletes to
whole apps node, which triggers some sort of reconfiguration behind the scenes,
which are visible mostly on Jenkins due to lower processing power. A typical
stack trace is
java.io.IOException: mkdir(http://localhost:45228/apps) failed, status code=503
at
org.apache.sling.commons.testing.integration.SlingIntegrationTestClient.mkdir(SlingIntegrationTestClient.java:69)
at
org.apache.sling.commons.testing.integration.SlingIntegrationTestClient.mkdirs(SlingIntegrationTestClient.java:87)
at
org.apache.sling.launchpad.webapp.integrationtest.servlets.resolver.errorhandler.ErrorHandlingTest.setUp(ErrorHandlingTest.java:58)
at junit.framework.TestCase.runBare(TestCase.java:132)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:36)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at
org.apache.sling.launchpad.testing.LoggingSuite.runTest(LoggingSuite.java:56)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.apache.sling.launchpad.testing.LoggingSuite.run(LoggingSuite.java:46)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
--
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
