[
https://issues.apache.org/jira/browse/SLING-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739697#comment-13739697
]
Robert Munteanu commented on SLING-2963:
----------------------------------------
This seems to happen every now and then unfortunately. I've attached a
sling.log file from a failing Jenkins build - see [^sling.log] .
My intuition is that the first time the test file is uploaded there is an
asynchronous action - perhaps setting up the server-side test fixture which is
not complete by the time the tests are executed.
I think there are two approaches to this
* Have the JUnit Remote test runner wait ( with a 1-5s timeout ) until the
execution result is as expected - e.g. not dumped by the
PlainTextRendererServlet
* Have the Test case wait until the result is as expected - e.g. not dumped by
the PlainTextRendererServlet
[~bdelacre] - what are your thoughts on this?
> IT failure: ScriptableTestsTest.testScriptableTest : Expected 0 failing tests
> but got 1
> ---------------------------------------------------------------------------------------
>
> Key: SLING-2963
> URL: https://issues.apache.org/jira/browse/SLING-2963
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Reporter: Robert Munteanu
> Attachments: error.log.gz, sling.log
>
>
> This test failed in build #1737 [0]
> java.lang.AssertionError: Expected 0 failing tests but got 1:
> [verifyContent[0](org.apache.sling.junit.scriptable.TestAllPaths): Unexpected
> content at path /apps/testing/ScriptableTests/testnode.test.txt, should be
> just TEST_PASSED (lines starting with # and empty lines are ignored)
> content was:
> ** Resource dumped by PlainTextRendererServlet**
> Resource path:/apps/testing/ScriptableTests/testnode
> Resource metadata: {sling.resolutionPathInfo=.test.txt,
> sling.resolutionPath=/apps/testing/ScriptableTests/testnode}
> Resource type: testing/ScriptableTests
> Resource super type: -
> ** Resource properties **
> sling:resourceType: testing/ScriptableTests
> jcr:createdBy: admin
> jcr:mixinTypes: [sling:Test]
> jcr:created:
> java.util.GregorianCalendar[time=1373560221155,areFieldsSet=true,areAllFieldsSet=true,lenient=false,zone=sun.util.calendar.ZoneInfo[id="GMT",offset=0,dstSavings=0,useDaylight=false,transitions=0,lastRule=null],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2013,MONTH=6,WEEK_OF_YEAR=28,WEEK_OF_MONTH=2,DAY_OF_MONTH=11,DAY_OF_YEAR=192,DAY_OF_WEEK=5,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=4,HOUR_OF_DAY=16,MINUTE=30,SECOND=21,MILLISECOND=155,ZONE_OFFSET=0,DST_OFFSET=0]
> jcr:primaryType: sling:Folder
> ]
> at org.junit.Assert.fail(Assert.java:91)
> at
> org.apache.sling.testing.samples.integrationtests.serverside.scriptable.ScriptableTestsTest.testScriptableTest(ScriptableTestsTest.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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
> 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.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at com.sun.proxy.$Proxy0.invoke(Unknown Source)
> at
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> [0]:
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/1737/testReport/org.apache.sling.testing.samples.integrationtests.serverside.scriptable/ScriptableTestsTest/testScriptableTest_0_/
--
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
