On 10/23/2013 12:30 PM, Lorenzo Bettini wrote:
Since failures seem to be related to shells, probably we should wait
for shells to close?
That sounds like a possible fix.
The problem is how to debug such situations, or understand where the
problem is in such a huge suite; not to mention that this happens during
the maven build...
The error report shows you the test that is failing.
is there a way to tell mvn to execute a single test
(or a set of tests)?
Yes, just add "-Dtest=org.eclipse.swtbot.TestClassName" to the command
line when running Maven.
it's kind of strange that I'm the only one experiencing that... my
laptop is a quad-core but it's two years old, I guess there are faster
machines around there nowadays ;)
Yes. But that kind of thing doesn't depend only on hardware, and can for
example depend on the window manager or other stuff. I didn't hear about
a similar issue so far.
--
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>
_______________________________________________
swtbot-dev mailing list
swtbot-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/swtbot-dev
