Eclipse Community Forums: SWTBot » metacity sometimes makes SWTBot tests fail in Jenkins

Help

Home

Home » Eclipse Projects » SWTBot » metacity sometimes makes SWTBot tests fail in Jenkins

Show: Today's Messages :: Show Polls :: Message Navigator

metacity sometimes makes SWTBot tests fail in Jenkins [message #1405974]

Fri, 08 August 2014 17:05

Lorenzo Bettini

Messages: 1763
Registered: July 2009
Location: Firenze, Italy

Senior Member

Hi

in all my Jenkins job that use SWTBot I have a preliminary build step
executing

metacity --replace --sm-disable &

(The jobs also start Xvnc)

This is an old machine and so it's slow.

Sometimes, the log of the job shows something like

+ metacity --replace --sm-disable<main build steps>

or

+ metacity --replace<main build steps>

and NOT

+ metacity --replace --sm-disable
<main build steps>

Thus, it looks like metacity does not correctly start, and of course,
all SWTBot tests that require a Shell (e.g., accessing a menu) fail...

Has anyone experienced a similar behavior?
Or has anyone have suggestions to avoid such behavior?

thanks in advance
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition

Report message to a moderator

Re: metacity sometimes makes SWTBot tests fail in Jenkins [message #1409577 is a reply to message #1405974]

Mon, 18 August 2014 12:50

Mickael Istria

Messages: 851
Registered: July 2009
Location: Grenoble, France

Senior Member

Hi,

I think you can configure the .xsession of the Jenkins user to start a
window manager (can be metacity, or unity, or whatever known to work
well with SWT) as it starts a X server.
So just starting Xvnc would automatically start the window manager and
you can get rid of the step to start the window manager.

HTH
--
Mickael Istria
My job: http://www.jboss.org/tools
My blog: http://mickaelistria.wordpress.com
My Tweets: http://twitter.com/mickaelistria

Report message to a moderator

Re: metacity sometimes makes SWTBot tests fail in Jenkins [message #1411121 is a reply to message #1409577]

Fri, 22 August 2014 12:51

Lorenzo Bettini

Messages: 1763
Registered: July 2009
Location: Firenze, Italy

Senior Member

On 18/08/2014 14:50, Mickael Istria wrote:
> Hi,
>
> I think you can configure the .xsession of the Jenkins user to start a
> window manager (can be metacity, or unity, or whatever known to work
> well with SWT) as it starts a X server.
> So just starting Xvnc would automatically start the window manager and
> you can get rid of the step to start the window manager.
>
> HTH

Thanks for the suggestion, I'll investigate that and keep you posted.

cheers
LOrenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

Report message to a moderator

Previous Topic:	Difference of click() in the test thread vs. wrapping its execution in syncExec()?
Next Topic:	How to test NatTable using swtbot?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Jul 14 07:59:33 GMT 2020

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter