[jbosstools-dev] Ways to increase tycho timeouts
Rob Stryker
rstryker at redhat.com
Tue Aug 14 01:10:39 EDT 2012
My tests already do disable and re-enable the validator framework, yes.
They use the line:
org.eclipse.wst.validation.ValidationFramework.getDefault().suspendAllValidation(true);
This is re-enabled after the test is over. This cut down most tests from
something like 35 seconds to a mere 5 or 10. So this was very useful.
Without this line, a full suite would be completely impossible.
I've tried to get an estimate of how long the full suite takes to run,
but I'm having difficulty. I've added the following to my test's pom.xml:
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-surefire-plugin</artifactId>
<version>${tychoVersion}</version>
<configuration>
+ <surefire.timeout>10800</surefire.timeout>
<testSuite>org.jboss.tools.as.test.core</testSuite>
<testClass>org.jboss.tools.as.test.core.ASToolsTestSuite</testClass>
</configuration>
</plugin>
If I set the timeout to something large, the suite still shuts off
exactly at 42 minutes. If I set the timeout to something small, like
500, it cuts off early as expected. So the problem here seems I can
override the setting, but only to make it shorter (??), not longer. If
I'm wrong, then I have absolutely no way to explain the current behaviour.
Unexplainably, even though the suite ends by "terminating the process",
the test suite continues to run in the background. The eclipse instance
is still open and continues to run. I set up a process watcher to alert
me when the java process finally ended. IT seems the current suite was
terminated at 12:20 after a 42 minute run, and finally ended at 12:56.
So that's 42+36=78 minutes. The test suite currently takes 78 minutes.
But of course I expect to add more tests. And the duration will just grow.
On 08/13/2012 07:28 PM, Max Rydahl Andersen wrote:
> Rob - what are the builders that are taking time?
>
> for your tests you don't really need much builders/validators to run do you ?
>
> Have you looked at disabling the parts you dont need for quicker turnaround ?
>
> /max
>
> On 07 Aug 2012, at 13:39, Rob Stryker <rstryker at redhat.com> wrote:
>
>> Yes... teh tests wait in UI thread a lot. This is because they need to
>> wait for jobs to finish. THe test suite involves things like creating
>> about 2000 dynamic web projects. It also does lots of resource changing,
>> and needs to wait for builders to complete, for classes to compile, and
>> for publish jobs to ... publish.
>>
>> The test is functioning exactly as intended. The suite, by design, waits
>> a lot. That's what it needs to do. It has a lot of work to do and it
>> needs to make sure all the work is being done. Builders need to execute.
>> Validators need to validate. Publishers need to calculate deltas and
>> publish. Most of these tasks are kicked off via the UI thread, but get
>> punted into some background worker. But the UI thread must continue to
>> wait for the jobs to finish before they can check if the results are
>> correct.
>>
>> Can we please have some way to get this changed? Is there a way? I can
>> promise you that my test suite *does* need all of this time waiting. The
>> various jobs need to execute before I can verify results, and that
>> invovles the UI thread waiting for the jobs to finish.
>>
>> Max, any ideas here? Mistria? The ever-missing Nick Boldt?
>>
>> On 08/04/2012 09:01 AM, Denis Golovin wrote:
>>> Execution of org.jboss.tools.as.test.core killed after 1 hour for my
>>> local build.
>>> I added counter for milliseconds inside delay() function. It says
>>> as.test.core spent about half an hour just waiting in UI thread (see
>>> console output below).
>>>
>>> .....
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest:
>>> org.jboss.ide.eclipse.as.71, unzipped, server, permod_absolute
>>> 2092900
>>> 2093403
>>> 2093906
>>> 2, 2, 2
>>> 2094411
>>> 2094411
>>> 2094411
>>> 1, 1, 1
>>> 2094914
>>> 2094914
>>> 2094914
>>> 1, 1, 1
>>> 2094914
>>> 2095417
>>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest:
>>> org.jboss.ide.eclipse.as.71, unzipped, server, permod_relative
>>> 2095417
>>> 2095920
>>> 2096422
>>> 2, 2, 2
>>> Process 1344039098433 is killed.
>>> .....
>>> [INFO] org.jboss.ide.eclipse.as.test ..................... SUCCESS
>>> [1:07.454s]
>>> [INFO] org.jboss.ide.eclipse.as.archives.integration.test SUCCESS
>>> [2:10.718s]
>>> [INFO] org.jboss.ide.eclipse.as.management.as7.tests ..... SUCCESS [18.715s]
>>> [INFO] org.jboss.tools.as.test.core ...................... FAILURE
>>> [1:01:45.285s]
>>> [INFO] org.jboss.ide.eclipse.as.ui.test .................. SUCCESS [17.633s]
>>> [INFO] as.features ....................................... SUCCESS [0.054s]
>>> [INFO] org.jboss.ide.eclipse.as.serverAdapter.wtp.feature SUCCESS [3.262s]
>>> [INFO] org.jboss.ide.eclipse.as.archives.integration.feature SUCCESS
>>> [1.519s]
>>> [INFO] org.jboss.ide.eclipse.as.jmx.integration.feature .. SUCCESS [1.573s]
>>> [INFO] org.jboss.ide.eclipse.as.server.rse.integration.feature SUCCESS
>>> [1.494s]
>>> [INFO] org.jboss.ide.eclipse.as.feature .................. SUCCESS [1.608s]
>>> [INFO] org.jboss.ide.eclipse.as.test.feature ............. SKIPPED
>>> [INFO] as.site ........................................... SKIPPED
>>>
>>>
>>> Denis
>>>
>>> On 08/03/2012 11:07 AM, Denis Golovin wrote:
>>>> Rob,
>>>>
>>>> I wondering why it takes so long to test.
>>>> What test are you talking about?
>>>> Does it include SWT Bot tests?
>>>> Most likely it uses delay() function to much and that's why it takes so
>>>> long.
>>>>
>>>> Best
>>>> Denis
>>>>
>>>> On 08/03/2012 01:03 AM, Rob Stryker wrote:
>>>>> Hi all:
>>>>>
>>>>> I've recently added a new test suite to astools, and when run locally
>>>>> via tycho, it times out after 40 minutes. My test suite requires longer
>>>>> than that to run, so I was wondering if there's any way to increase this
>>>>> timeout.
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
More information about the jbosstools-dev
mailing list