SWTBot hanging in Jenkins [message #1232154] |
Thu, 16 January 2014 05:12  |
Eclipse User |
|
|
|
Hi,
We have integerated successfully SWTBot with Jenkins by following the instruction over here - http://wiki.eclipse.org/SWTBot/Automate_test_execution#On_Jenkins
Now all of sudden after adding few more testcases all of them started hanging in Jenkins. We are able to run the same testcases locally (both Windows and Linux) without any issues but the same hangs in Jenkins.
Tried several things and finally found out that there is something to do with the testcase which we have written. Basically all these testcases are done to check the shortcuts working in table. For eg. Delete key to delete a row, Insert key to insert new row and so on. and during the execution of one of the shortcuts entire eclipse just hangs and in turn whole jenkins build just hangs.
Can someone provide suggestions or possible fix for this issue?
Thanks.
|
|
|
|
|
|
|
|
|
|
|
Re: SWTBot hanging in Jenkins [message #1235409 is a reply to message #1235320] |
Fri, 24 January 2014 04:22   |
Eclipse User |
|
|
|
On 01/24/2014 04:48 AM, Melwyn Jensen wrote:
> Sorry for my ignorance Mickael, I was under the impression that there is
> a separate team for SWTBot.
No problem, it's not made explicit how and by who the SWTBot project
happens to be developed. And actually, it's not set in stone: it can
change one day.
I believe individual contributors who contribute sporadically to SWTBot
can take the comparison with an organized team as a compliment ;)
> Quote:
>> Did you report a bug on this topic? If so, did you try to write a
>> sample example to reproduce the issue, automate it as a test, provide
>> a patch...?
>
> Am afraid if I will be able to create a sample example because as I said
> earlier the issue is with only jenkins build and not when testing it
> locally. I just pointed out that it might be a SWTBot issue but still
> not able to figure out 100% the exact cause for it.
I believe it could be an issue with the mapping of keys in Xvnc. Some
versions of Xvnc are know to have glitches regarding mouse or keyboard
events.
Maybe you should try it locally using Xvnc. Make sure the local Xvnc is
the same as the one on your CI machine.
Anyway, it's always good to track issues in a bug. It's easier to find
them and it's easier for people to continue discussion. If it happens
that the issue in not in SWTBot, we'll simply explain the cause, close
the bug as NOT_ECLIPSE. No damage will happen.
--
Mickael Istria
My job: http://www.jboss.org/tools
My blog: http://mickaelistria.wordpress.com
My Tweets: http://twitter.com/mickaelistria
|
|
|
|
Powered by
FUDForum. Page generated in 0.40740 seconds