[jbosstools-dev] Ways to increase tycho timeouts
Max Rydahl Andersen
max.andersen at redhat.com
Mon Aug 13 07:28:14 EDT 2012
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