<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Thanks Mickael:<br>
<br>
Using the cmd line arg worked properly. Full test suite took 1
hour 20 minutes and currently has 36 failures and 800 errors
(erm... hrmm). Guess I'll need to investigate what went wrong
suddenly that wasn't going wrong in PDE. <br>
<br>
Also, for anyone using parametized tests, junit's a little vague
on what exactly is going on, so make sure your assertion error
messages are very descriptive and include lots of information.
Otherwise you won't even know what parameters your test was
constructed with :|<br>
<br>
- Rob<br>
<br>
On 08/14/2012 05:25 PM, Mickael Istria wrote:<br>
</div>
<blockquote cite="mid:502A196C.1090905@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 08/14/2012 07:10 AM, Rob Stryker
wrote:<br>
</div>
<blockquote cite="mid:5029DDCF.1040209@redhat.com" type="cite">
<pre wrap="">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>
</pre>
</blockquote>
With surefire, the right argument for timeout is
forkedProcessTimeoutInSeconds ( <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://www.eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/test-mojo.html#forkedProcessTimeoutInSeconds">http://www.eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/test-mojo.html#forkedProcessTimeoutInSeconds</a>
). But with <a moz-do-not-send="true"
href="https://issues.jboss.org/browse/JBIDE-12422">JBIDE-12422</a>,
I made the necessary changes so you don't have to modify pom.xml
anymore to try new timeouts. Passing <i>-Dsurefire.timeout=10800</i>
to command-line will now work (property surefire.timeout is the
default value for forkedProcessTimeoutInSeconds when not set in
configuration). When you think you found a timeout that is fine
for most cases, you can modify the value of the surefire.timeout <b>property</b>
(not argument in tycho-surefire-plugin configure) to the value you
think is the best.<br>
Default value, set in parent pom, for surefire.timeout is 2400
seconds (40 minutes), but it is often overriden in
project-specific pom.<br>
Once again, let me insist that you should use the surefire.timeout
property rather than the forkedProcessTimeoutInSeconds argument.<br>
<br>
You should perform a local update to leverage these changes.
Feedback is, as always, welcome.<br>
<br>
<blockquote cite="mid:5029DDCF.1040209@redhat.com" type="cite">
<pre wrap="">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.</pre>
</blockquote>
That's weird, but I think this issue disappeared with changes for
JBIDE-12422<br>
<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a moz-do-not-send="true"
href="http://www.jboss.org/tools">JBoss, by Red Hat</a><br>
<a moz-do-not-send="true"
href="http://mickaelistria.wordpress.com">My blog</a> - <a
moz-do-not-send="true" href="http://twitter.com/mickaelistria">My
Tweets</a></div>
</blockquote>
<br>
<br>
</body>
</html>