[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tracecompass-dev] Build instability meta-bug
|
Yes, thanks. I should make this more clear. We do force GTK2 for our normal builds. We're still working on getting GTK3 to work, in collaboration with SWT and SWTBot. Forcing GTK2 can't be a work around forever...hopefully. Also, the packages (EPP) all use GTK3 by default so there is incentive on making this work.
Marc-Anre
________________________________________
From: tracecompass-dev-bounces@xxxxxxxxxxx [tracecompass-dev-bounces@xxxxxxxxxxx] on behalf of Oberhuber, Martin [Martin.Oberhuber@xxxxxxxxxxxxx]
Sent: Wednesday, 27 January 2016 9:31 AM
To: tracecompass developer discussions
Subject: Re: [tracecompass-dev] Build instability meta-bug
Have you tried launching
eclipse --launcher.GTK_Version 2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436558
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
-----Original Message-----
From: tracecompass-dev-bounces@xxxxxxxxxxx [mailto:tracecompass-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc-André Laperle
Sent: Thursday, January 21, 2016 12:29 AM
To: tracecompass developer discussions
Subject: Re: [tracecompass-dev] Build instability meta-bug
I think 3 of them are GTK3 only. I have done some progress on this but there are multiple problems (bugs in SWT, SWTBot and possibly GTK). It think those might not get fixed in the short term unless someone feels strongly about supporting GTK3. I can still add them to keep track.
________________________________________
From: tracecompass-dev-bounces@xxxxxxxxxxx [tracecompass-dev-bounces@xxxxxxxxxxx] on behalf of Alexandre Montplaisir [alexmonthy@xxxxxxxxxxxx]
Sent: Wednesday, 20 January 2016 6:24 PM
To: tracecompass-dev@xxxxxxxxxxx
Subject: Re: [tracecompass-dev] Build instability meta-bug
On 2016-01-20 06:07 PM, Matthew Khouzam wrote:
> Hi all,
>
> Our build on hudson is pretty stable, but not 100% stable. In order to
> fix this, we need to first identify what is at fault. If anyone sees a
> build failure NOT triggered by their code, therefore not a legit
> failure (tm), please make it block bug 486207.
Hyperlink for the lazy, like myself ;)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=486207
Very good initiative!
Even our big matrix build using many different configurations is down to only 4 failing tests:
https://ci.lttng.org/view/Trace%20Compass/job/tracecompass-master-linux/144/#showFailuresLink
Alex
>
> We are working towards improving the build, your help is ALWAYS appreciated.
>
> Matthew
> _______________________________________________
> tracecompass-dev mailing list
> tracecompass-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
