|
|
|
|
|
|
|
Re: SWTBot hanging in Jenkins [message #1234745 is a reply to message #1234514] |
Wed, 22 January 2014 18:09 |
|
On 01/22/2014 07:24 AM, Melwyn Jensen wrote:
> Seems to be a limitation in SWTBot. It will be good if the next release
> have some fix on this as well
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...?
> and also reply from SWTBot Development
> team will be highly appreciable cause tried mailing them but didn't get
> reply after sometime.
Your question is related to usage, the swtbot-dev mailing-list is
dedicated to development issues. So it fits better on the forum than on
the mailing-list.
Beware that there is no such "SWTBot Development Team", it's just some
individuals who contribute as they can/want/need to SWTBot. People are
busy, asking them to be more available is generally useless.
Contributors as as much available as they can be.
Cheers,
--
Mickael Istria
My job: http://www.jboss.org/tools
My blog: http://mickaelistria.wordpress.com
My Tweets: http://twitter.com/mickaelistria
|
|
|
Re: SWTBot hanging in Jenkins [message #1235320 is a reply to message #1234745] |
Fri, 24 January 2014 03:48 |
Melwyn Jensen Messages: 15 Registered: January 2014 |
Junior Member |
|
|
Sorry for my ignorance Mickael, I was under the impression that there is a separate team for SWTBot.
> 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. Sure will try to pitch in for the fix when I find out the real cause of the problem.
Thanks!
[Updated on: Fri, 24 January 2014 03:50] Report message to a moderator
|
|
|
Re: SWTBot hanging in Jenkins [message #1235409 is a reply to message #1235320] |
Fri, 24 January 2014 09:22 |
|
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.04350 seconds