> Just a quick note, Patrick pushed the following commit:
> https://git.eclipse.org/r/9744
> which should hopefully solve the deadlock issue.
Hey,
I saw this review and assumed it fixed the issue as a few other builds
succeeded afterwards. However, just this morning I noticed another
hanging buil
Just a quick note, Patrick pushed the following commit:
https://git.eclipse.org/r/9744
which should hopefully solve the deadlock issue.
Have a nice weekend all,
Alex
On 13-01-17 02:30 PM, Patrick Tasse wrote:
> Hi Roland,
>
> I'm able to reproduce the hanging intermittently, there seems to be a
Hi Roland,
I'm able to reproduce the hanging intermittently, there seems to be a
timing-dependent deadlock in our code. I'll try to submit a fix asap.
Patrick
On Thu, Jan 17, 2013 at 2:12 PM, Roland Grunberg wrote:
> The build seems to have progressed beyond AllTmfUITests. Did the commit
> for
The build seems to have progressed beyond AllTmfUITests. Did the commit
for https://git.eclipse.org/r/#/c/9699/ have anything to do with it ?
Cheers,
--
Roland Grunberg
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/m
> Hi Roland,
>
> When we run tmf.ui tests locally, it opens a separate Eclipse window
> in
> which some UI functionality is tested (mainly for the Sequence
> Diagram
That's perfectly fine. In fact quite a few of the UI tests, and
especially SWTBot tests make use of this. Hudson is configured
to s
Hi Roland,
When we run tmf.ui tests locally, it opens a separate Eclipse window in
which some UI functionality is tested (mainly for the Sequence Diagram
framework). Looking at the Hudson log, it ends on:
Xlib: extension "RANDR" missing on display ":108.0".
What I assume is happening is that the
Our hudson job that tracks the master branch started failing a few days
ago [1] on running :
org.eclipse.linuxtools.tmf.ui.tests.AllTmfUITests
After that all subsequent builds failed on running :
org.eclipse.linuxtools.changelog.core.tests.AllTests (1220-1227)
The problem with the Changelog Cor
