The timeout is directly overwritten in surefire configuation block,
so
it seems to ignore what is passed through command-line.
We should rewrite the way we configure timeouts to rely on the
surefire.timeout property, so it becomes possible to override it via
command-line.
On 08/13/2012 01:27 PM, Max Rydahl Andersen wrote:
> eh ?
>
> its trivial to override any setting in the test module pom.
>
> in this case its surefire.timeout.
>
> /max
>
> On 13 Aug 2012, at 10:29, Mickael Istria<mistria(a)redhat.com> wrote:
>
>> On 08/03/2012 10:03 AM, Rob Stryker wrote:
>>> Hi all:
>> Hi,
>>
>>> 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.
>>>
>> There is currently no way to change timeout except by changing it directly in
poms. Can you please open a feature request for that so we'll introduce a property?
>> --
>> Mickael Istria
>> Eclipse developer at JBoss, by Red Hat
>> My blog - My Tweets
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev