Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Ben Cooksley]

On Tue, Apr 26, 2016 at 8:51 AM, Albert Astals Cid  wrote:
> El dilluns, 25 d’abril de 2016, a les 19:14:00 CEST, Ben Cooksley va escriure:
>> On Mon, Apr 25, 2016 at 5:59 PM, Martin Graesslin 
> wrote:
>> > On Saturday, April 23, 2016 8:48:17 PM CEST Ben Cooksley wrote:
>> >> On Sat, Apr 23, 2016 at 8:35 PM, Martin Graesslin 
>> >
>> > wrote:
>> >> > On Saturday, April 23, 2016 1:09:00 PM CEST Ben Cooksley wrote:
>> >> >> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil 
> wrote:
>> >> >> > On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
>> >> >> >> On Fri, Apr 22, 2016 at 11:11 PM, David Faure 
> wrote:
>> >> >> >> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
>> >> >> >> >> GENERAL INFO
>> >> >> >> >>
>> >> >> >> >> BUILD UNSTABLE
>> >> >> >> >> Build URL:
>> >> >> >> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFOR
>> >> >> >> >> M=L
>> >> >> >> >> inu
>> >> >> >> >> x,
>> >> >> >> >> compiler=gcc/11/>
>> >> >> >> >
>> >> >> >> > Wow, ASAN detected a real bug in Qt here.
>> >> >> >> >
>> >> >> >> > Fixed in https://codereview.qt-project.org/156728
>> >> >> >>
>> >> >> >> As this issue essentially breaks any test on the CI system that
>> >> >> >> depends on Qt I suggest all developers affected by this indicate
>> >> >> >> this
>> >> >> >> on the relevant reviews.
>> >> >> >
>> >> >> > Hey guys,
>> >> >>
>> >> >> Hi David,
>> >> >>
>> >> >> > any chance to get this patch into our Qt build on the CI since it
>> >> >> > has
>> >> >> > been
>> >> >> > integrated upstream now? As it affects all tests that interact with
>> >> >> > DBus
>> >> >> > it
>> >> >> > would be nice to resolve this on the CI.
>> >> >>
>> >> >> We'll need upstream to update qt5.git (I think that's still required
>> >> >> for changes to fully flow through) I think.
>> >> >> We could try to hack the patch in, but then we'll end up having to
>> >> >> undo that in a few weeks time.
>> >> >
>> >> > Could we disable that ASAN check please[1]? I have two of my projects
>> >> > failing due to the DBus problem and one further failing due to a
>> >> > similar
>> >> > problem in QQuickStyleItem [2]. It's nice that we find errors, but I
>> >> > rather not have my tests fail due to errors in Qt.
>> >>
>> >> That would just cover up the issue.
>> >
>> > Yes it would and that's exactly what I want.
>> >
>> > To me the CI is currently producing false positives. It started to break
>> > from one moment to the other. It costs time to look into why it started
>> > to fail. It means that till that problem is fixed in Qt I cannot trust
>> > the CI system. It results in nobody noticing real breakage, because the
>> > build is broken anyway.
>> >
>> > Then there is the problem of responsibility: I look at the output, I have
>> > no idea why that thing is broken, I have no idea how to build a minimal
>> > example which would reproduce it, even less on how to fix it. That's just
>> > a really bad situation to have a CI which can be trusted.
>> >
>> > In summary: I don't want spend time to investigate false positives. If an
>> > option results in false positives, I think that we should disable it.
>>
>> Understandable.
>>
>> > Of course Qt should get those bugs fixed, but for that Qt should enable
>> > ASAN on their CI system. If we get libraries which are free of ASAN
>> > problems, then we can enable it on our side. But false positives are just
>> > bad.
>>
>> Based on this i'm going to assume Qt is not ASAN compliant, and will
>> therefore be disabling ASAN for all KDE projects across the entire KDE
>> CI system in 24 hours unless nobody objects.
>
> Instead of an axe let's be more precise and disable the check that's giving us
> problems
>
> https://phabricator.kde.org/D1489
>
> And reenable it in a month.

This has now been done.
If someone could send a reminder once the fix has made it's way into
qt5.git that would be much appreciated.

>
> Cheers,
>   Albert

Thanks,
Ben

>
>>
>> Objectors can be expected to place pressure on the appropriate
>> processes within the Qt Project to:
>> a) Get the necessary changes flowed through into qt5.git so we can
>> pick them up (the existing process is painfully slow)
>> b) Get their CI system to check for ASAN issues.
>>
>> > Cheers
>> > Martin
>>
>> Regards,
>> Ben
>> ___
>> Kde-frameworks-devel mailing list
>> Kde-frameworks-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>
>
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Albert Astals Cid]

El dilluns, 25 d’abril de 2016, a les 19:14:00 CEST, Ben Cooksley va escriure:
> On Mon, Apr 25, 2016 at 5:59 PM, Martin Graesslin  
wrote:
> > On Saturday, April 23, 2016 8:48:17 PM CEST Ben Cooksley wrote:
> >> On Sat, Apr 23, 2016 at 8:35 PM, Martin Graesslin 
> > 
> > wrote:
> >> > On Saturday, April 23, 2016 1:09:00 PM CEST Ben Cooksley wrote:
> >> >> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  
wrote:
> >> >> > On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
> >> >> >> On Fri, Apr 22, 2016 at 11:11 PM, David Faure  
wrote:
> >> >> >> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
> >> >> >> >> GENERAL INFO
> >> >> >> >> 
> >> >> >> >> BUILD UNSTABLE
> >> >> >> >> Build URL:
> >> >> >> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFOR
> >> >> >> >> M=L
> >> >> >> >> inu
> >> >> >> >> x,
> >> >> >> >> compiler=gcc/11/>
> >> >> >> > 
> >> >> >> > Wow, ASAN detected a real bug in Qt here.
> >> >> >> > 
> >> >> >> > Fixed in https://codereview.qt-project.org/156728
> >> >> >> 
> >> >> >> As this issue essentially breaks any test on the CI system that
> >> >> >> depends on Qt I suggest all developers affected by this indicate
> >> >> >> this
> >> >> >> on the relevant reviews.
> >> >> > 
> >> >> > Hey guys,
> >> >> 
> >> >> Hi David,
> >> >> 
> >> >> > any chance to get this patch into our Qt build on the CI since it
> >> >> > has
> >> >> > been
> >> >> > integrated upstream now? As it affects all tests that interact with
> >> >> > DBus
> >> >> > it
> >> >> > would be nice to resolve this on the CI.
> >> >> 
> >> >> We'll need upstream to update qt5.git (I think that's still required
> >> >> for changes to fully flow through) I think.
> >> >> We could try to hack the patch in, but then we'll end up having to
> >> >> undo that in a few weeks time.
> >> > 
> >> > Could we disable that ASAN check please[1]? I have two of my projects
> >> > failing due to the DBus problem and one further failing due to a
> >> > similar
> >> > problem in QQuickStyleItem [2]. It's nice that we find errors, but I
> >> > rather not have my tests fail due to errors in Qt.
> >> 
> >> That would just cover up the issue.
> > 
> > Yes it would and that's exactly what I want.
> > 
> > To me the CI is currently producing false positives. It started to break
> > from one moment to the other. It costs time to look into why it started
> > to fail. It means that till that problem is fixed in Qt I cannot trust
> > the CI system. It results in nobody noticing real breakage, because the
> > build is broken anyway.
> > 
> > Then there is the problem of responsibility: I look at the output, I have
> > no idea why that thing is broken, I have no idea how to build a minimal
> > example which would reproduce it, even less on how to fix it. That's just
> > a really bad situation to have a CI which can be trusted.
> > 
> > In summary: I don't want spend time to investigate false positives. If an
> > option results in false positives, I think that we should disable it.
> 
> Understandable.
> 
> > Of course Qt should get those bugs fixed, but for that Qt should enable
> > ASAN on their CI system. If we get libraries which are free of ASAN
> > problems, then we can enable it on our side. But false positives are just
> > bad.
> 
> Based on this i'm going to assume Qt is not ASAN compliant, and will
> therefore be disabling ASAN for all KDE projects across the entire KDE
> CI system in 24 hours unless nobody objects.

Instead of an axe let's be more precise and disable the check that's giving us 
problems

https://phabricator.kde.org/D1489

And reenable it in a month.

Cheers,
  Albert

> 
> Objectors can be expected to place pressure on the appropriate
> processes within the Qt Project to:
> a) Get the necessary changes flowed through into qt5.git so we can
> pick them up (the existing process is painfully slow)
> b) Get their CI system to check for ASAN issues.
> 
> > Cheers
> > Martin
> 
> Regards,
> Ben
> ___
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel


___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Martin Graesslin]

On Saturday, April 23, 2016 10:35:22 AM CEST Martin Graesslin wrote:
> Could we disable that ASAN check please[1]? I have two of my projects
> failing due to the DBus problem and one further failing due to a similar
> problem in QQuickStyleItem [2]. It's nice that we find errors, but I rather
> not have my tests fail due to errors in Qt.

Just for the record: plasma-workspace is also failing due to that.

Cheers
Martin

signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Martin Graesslin]

On Monday, April 25, 2016 11:17:03 AM CEST Luigi Toscano wrote:
> On Monday 25 of April 2016 19:14:00 Ben Cooksley wrote:
> > On Mon, Apr 25, 2016 at 5:59 PM, Martin Graesslin 
> 
> wrote:
> > > In summary: I don't want spend time to investigate false positives. If
> > > an
> > > option results in false positives, I think that we should disable it.
> > 
> > Understandable.
> > 
> > > Of course Qt should get those bugs fixed, but for that Qt should enable
> > > ASAN on their CI system. If we get libraries which are free of ASAN
> > > problems, then we can enable it on our side. But false positives are
> > > just
> > > bad.
> > 
> > Based on this i'm going to assume Qt is not ASAN compliant, and will
> > therefore be disabling ASAN for all KDE projects across the entire KDE
> > CI system in 24 hours unless nobody objects.
> 
> The best of both worlds would be leave it enabled, but weave the known
> faulty results until they are fixed. Notification emails would come only
> for new issues. This happens in OpenStack, for example, where otherwise the
> amount of failures from underlying components would block too many projects
> for too much time (a skiplist disables few tests annotated with
> decorators).

Unfortunately that's not a solution in the case of the problems here. E.g. all 
my KWin/Wayland tests fail when connecting to DBus, that happens directly in 
init. No test is executed. It's like not having any tests at all.

Cheers
Martin


signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Martin Graesslin]

On Monday, April 25, 2016 7:29:51 AM CEST Albert Astals Cid wrote:
> I object.
> a) I already told you, don't use something nobody else uses, use the
> separate reposb) Not going to happen, but why would it matter at all?
> 
> More reasons for it: c) ASAN does not check for things in the library being
> broken or not since it only works on code compiled with ASAN, so the
> crashes are not in the library, they are in your code (if they are because
> of the library being broken or not that's not important, *your* code is the
> one that is going to crash)

Please check the backtraces. It's in this cases NOT a bug in "my code", it's a 
wrong delete in Qt code, making my test fail. Yes it's a bug, yes my code 
exposes it, yes I don't care, because there is nothing we can do. It's a false 
positive from my point of view. And makes it difficult to get real test 
results. 
A false positive destroys the purpose of a CI system. If we cannot trust it, 
it gets ignored.

Cheers
Martin

signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Ben Cooksley]

On Mon, Apr 25, 2016 at 7:29 PM, Albert Astals Cid <aa...@kde.org> wrote:
> I object.
>
> a) I already told you, don't use something nobody else uses, use the
> separate repos

Umm, since when? To my knowledge kdesrc-build uses qt5.git.
The Qt developers might not, but I don't care one bit what they do,
it's what we do that matters.

In any event, this would make updating Qt a complete and utter
nightmare, especially if inter-module building breaks at some point
(i've been told this is why qt5.git sometimes get stuck for
weeks/months without updates - so it definitely happens more often
than not).

I'd rather not be exposed to Qt politics between modules, because
they've broken their internal BC (and they'll break it, that much i'm
sure - they broke BC in the move from Qt 5.5 to 5.6 requiring a
rebuild of kdelibs4support so don't say the Qt developers know about
BC, because they don't. If they can't manage it for external
interfaces, they definitely won't be able to for "internal" ones)

Not to mention we have to get our build order right if things depend
on more than just qtcore (which i'm almost certain will be the case)

> b) Not going to happen, but why would it matter at all?
>
> More reasons for it:
>  c) ASAN does not check for things in the library being broken or not since
> it only works on code compiled with ASAN, so the crashes are not in the
> library, they are in your code (if they are because of the library being
> broken or not that's not important, *your* code is the one that is going to
> crash)

To my knowledge we don't compile Qt with ASAN support (considering one
has to tell the build system / compiler / linker to bring it in, and
we definitely don't do anything special here).
The backtraces quite clearly show that the code in question going bang
is deep inside Qt, and David confirmed that it's 100% a Qt bug and
nothing we can workaround.

>  d) Hiding your head in the sand and saying "this is not my fault it's Qt's
> fault" is not going to fix the fact that your code is crashing
>  e) We've uncovered bugs that otherwise would have bitten us and nobody
> would have bothered fixing because they would be hardly reproducible, both
> in our code and in Qt's code, that is a *good* thing, not a bad thing.

I'll agree that it's a good thing.
What's bad is that we have to deal with Qt, who as far as i'm
concerned at least are not responsive enough to our complaints, and
are far too slow.

>
>
> Let's not move backwards.
>
> Cheers,
>   Albert

Regards,
Ben

>
> 
> De: Ben Cooksley <bcooks...@kde.org>
> Para: Martin Graesslin <mgraess...@kde.org>
> CC: Scarlett Clark <sgcl...@kde.org>; "kde-frameworks-devel@kde.org"
> <kde-frameworks-devel@kde.org>
> Enviado: Lunes 25 de abril de 2016 9:14
> Asunto: Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build
> # 11 - Still Unstable!
>
> On Mon, Apr 25, 2016 at 5:59 PM, Martin Graesslin <mgraess...@kde.org>
> wrote:
>> On Saturday, April 23, 2016 8:48:17 PM CEST Ben Cooksley wrote:
>>> On Sat, Apr 23, 2016 at 8:35 PM, Martin Graesslin <mgraess...@kde.org>
>> wrote:
>>> > On Saturday, April 23, 2016 1:09:00 PM CEST Ben Cooksley wrote:
>>> >> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil <dvra...@kde.org>
>>> >> wrote:
>>> >> > On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
>>> >> >> On Fri, Apr 22, 2016 at 11:11 PM, David Faure <fa...@kde.org>
>>> >> >> wrote:
>>> >> >> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
>>> >> >> >> GENERAL INFO
>>> >> >> >>
>>> >> >> >> BUILD UNSTABLE
>>> >> >> >> Build URL:
>>> >> >> >>
>>> >> >> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=L
>>> >> >> >> inu
>>> >> >> >> x,
>>> >> >> >> compiler=gcc/11/>
>>> >> >> >
>>> >> >> > Wow, ASAN detected a real bug in Qt here.
>>> >> >> >
>>> >> >> > Fixed in https://codereview.qt-project.org/156728
>>> >> >>
>>> >> >> As this issue essentially breaks any test on the CI system that
>>> >> >> depends on Qt I suggest all developers affected by this indicate
>>> >> >> this
>>> >> >> on the relevant reviews.
>>> >> >
>>> >> > Hey guys,
>>> >>
>>> >&g

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Kevin Ottens]

Hello,

On Monday, 25 April 2016 07:29:51 CEST Albert Astals Cid wrote:
> I object.
> a) I already told you, don't use something nobody else uses, use the
> separate repos

I think you're making that up to some extend, it's used and tested, more than 
all the possible combinations of using the separate repositories.

Note that I'm not saying we shouldn't use separate repositories, I'm just 
saying your argument isn't a good one.

Now, with the relationship we have with Qt, using the separate repositories on 
release branches make sense to me, exactly for this kind of situations when we 
want a fix faster.

> b) Not going to happen, but why would it matter at all?
> 
> More reasons for it: c) ASAN does not check for things in the library being
> broken or not since it only works on code compiled with ASAN, so the
> crashes are not in the library, they are in your code (if they are because
> of the library being broken or not that's not important, *your* code is the
> one that is going to crash) d) Hiding your head in the sand and saying
> "this is not my fault it's Qt's fault" is not going to fix the fact that
> your code is crashing e) We've uncovered bugs that otherwise would have
> bitten us and nobody would have bothered fixing because they would be
> hardly reproducible, both in our code and in Qt's code, that is a *good*
> thing, not a bad thing.
> 
> Let's not move backwards.

I fully agree with the rest though. Let's not use a rushed upgrade to 5.6 
because of another massive screw up in PIM as an excuse to reduce our checks. 
We wouldn't be there if sysadmins could have done the upgrade on their own 
agenda not one forced upon them.

Regards.
-- 
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud supporter of KDE, http://www.kdab.com



signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Albert Astals Cid]

I object.
a) I already told you, don't use something nobody else uses, use the separate 
reposb) Not going to happen, but why would it matter at all?

More reasons for it: c) ASAN does not check for things in the library being 
broken or not since it only works on code compiled with ASAN, so the crashes 
are not in the library, they are in your code (if they are because of the 
library being broken or not that's not important, *your* code is the one that 
is going to crash)
 d) Hiding your head in the sand and saying "this is not my fault it's Qt's 
fault" is not going to fix the fact that your code is crashing
 e) We've uncovered bugs that otherwise would have bitten us and nobody would 
have bothered fixing because they would be hardly reproducible, both in our 
code and in Qt's code, that is a *good* thing, not a bad thing.

Let's not move backwards.

Cheers,  Albert

  De: Ben Cooksley <bcooks...@kde.org>
 Para: Martin Graesslin <mgraess...@kde.org> 
CC: Scarlett Clark <sgcl...@kde.org>; "kde-frameworks-devel@kde.org" 
<kde-frameworks-devel@kde.org>
 Enviado: Lunes 25 de abril de 2016 9:14
 Asunto: Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 
11 - Still Unstable!
   
On Mon, Apr 25, 2016 at 5:59 PM, Martin Graesslin <mgraess...@kde.org> wrote:
> On Saturday, April 23, 2016 8:48:17 PM CEST Ben Cooksley wrote:
>> On Sat, Apr 23, 2016 at 8:35 PM, Martin Graesslin <mgraess...@kde.org>
> wrote:
>> > On Saturday, April 23, 2016 1:09:00 PM CEST Ben Cooksley wrote:
>> >> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil <dvra...@kde.org> wrote:
>> >> > On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
>> >> >> On Fri, Apr 22, 2016 at 11:11 PM, David Faure <fa...@kde.org> wrote:
>> >> >> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
>> >> >> >> GENERAL INFO
>> >> >> >>
>> >> >> >> BUILD UNSTABLE
>> >> >> >> Build URL:
>> >> >> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=L
>> >> >> >> inu
>> >> >> >> x,
>> >> >> >> compiler=gcc/11/>
>> >> >> >
>> >> >> > Wow, ASAN detected a real bug in Qt here.
>> >> >> >
>> >> >> > Fixed in https://codereview.qt-project.org/156728
>> >> >>
>> >> >> As this issue essentially breaks any test on the CI system that
>> >> >> depends on Qt I suggest all developers affected by this indicate this
>> >> >> on the relevant reviews.
>> >> >
>> >> > Hey guys,
>> >>
>> >> Hi David,
>> >>
>> >> > any chance to get this patch into our Qt build on the CI since it has
>> >> > been
>> >> > integrated upstream now? As it affects all tests that interact with
>> >> > DBus
>> >> > it
>> >> > would be nice to resolve this on the CI.
>> >>
>> >> We'll need upstream to update qt5.git (I think that's still required
>> >> for changes to fully flow through) I think.
>> >> We could try to hack the patch in, but then we'll end up having to
>> >> undo that in a few weeks time.
>> >
>> > Could we disable that ASAN check please[1]? I have two of my projects
>> > failing due to the DBus problem and one further failing due to a similar
>> > problem in QQuickStyleItem [2]. It's nice that we find errors, but I
>> > rather not have my tests fail due to errors in Qt.
>>
>> That would just cover up the issue.
>
> Yes it would and that's exactly what I want.
>
> To me the CI is currently producing false positives. It started to break from
> one moment to the other. It costs time to look into why it started to fail. It
> means that till that problem is fixed in Qt I cannot trust the CI system. It
> results in nobody noticing real breakage, because the build is broken anyway.
>
> Then there is the problem of responsibility: I look at the output, I have no
> idea why that thing is broken, I have no idea how to build a minimal example
> which would reproduce it, even less on how to fix it. That's just a really bad
> situation to have a CI which can be trusted.
>
> In summary: I don't want spend time to investigate false positives. If an
> option results in false positives, I think that we should disable it.

Understandable.

>
> Of course Qt should get those bugs fixed, but for that Q

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Ben Cooksley]

On Mon, Apr 25, 2016 at 5:59 PM, Martin Graesslin  wrote:
> On Saturday, April 23, 2016 8:48:17 PM CEST Ben Cooksley wrote:
>> On Sat, Apr 23, 2016 at 8:35 PM, Martin Graesslin 
> wrote:
>> > On Saturday, April 23, 2016 1:09:00 PM CEST Ben Cooksley wrote:
>> >> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  wrote:
>> >> > On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
>> >> >> On Fri, Apr 22, 2016 at 11:11 PM, David Faure  wrote:
>> >> >> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
>> >> >> >> GENERAL INFO
>> >> >> >>
>> >> >> >> BUILD UNSTABLE
>> >> >> >> Build URL:
>> >> >> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=L
>> >> >> >> inu
>> >> >> >> x,
>> >> >> >> compiler=gcc/11/>
>> >> >> >
>> >> >> > Wow, ASAN detected a real bug in Qt here.
>> >> >> >
>> >> >> > Fixed in https://codereview.qt-project.org/156728
>> >> >>
>> >> >> As this issue essentially breaks any test on the CI system that
>> >> >> depends on Qt I suggest all developers affected by this indicate this
>> >> >> on the relevant reviews.
>> >> >
>> >> > Hey guys,
>> >>
>> >> Hi David,
>> >>
>> >> > any chance to get this patch into our Qt build on the CI since it has
>> >> > been
>> >> > integrated upstream now? As it affects all tests that interact with
>> >> > DBus
>> >> > it
>> >> > would be nice to resolve this on the CI.
>> >>
>> >> We'll need upstream to update qt5.git (I think that's still required
>> >> for changes to fully flow through) I think.
>> >> We could try to hack the patch in, but then we'll end up having to
>> >> undo that in a few weeks time.
>> >
>> > Could we disable that ASAN check please[1]? I have two of my projects
>> > failing due to the DBus problem and one further failing due to a similar
>> > problem in QQuickStyleItem [2]. It's nice that we find errors, but I
>> > rather not have my tests fail due to errors in Qt.
>>
>> That would just cover up the issue.
>
> Yes it would and that's exactly what I want.
>
> To me the CI is currently producing false positives. It started to break from
> one moment to the other. It costs time to look into why it started to fail. It
> means that till that problem is fixed in Qt I cannot trust the CI system. It
> results in nobody noticing real breakage, because the build is broken anyway.
>
> Then there is the problem of responsibility: I look at the output, I have no
> idea why that thing is broken, I have no idea how to build a minimal example
> which would reproduce it, even less on how to fix it. That's just a really bad
> situation to have a CI which can be trusted.
>
> In summary: I don't want spend time to investigate false positives. If an
> option results in false positives, I think that we should disable it.

Understandable.

>
> Of course Qt should get those bugs fixed, but for that Qt should enable ASAN 
> on
> their CI system. If we get libraries which are free of ASAN problems, then we
> can enable it on our side. But false positives are just bad.

Based on this i'm going to assume Qt is not ASAN compliant, and will
therefore be disabling ASAN for all KDE projects across the entire KDE
CI system in 24 hours unless nobody objects.

Objectors can be expected to place pressure on the appropriate
processes within the Qt Project to:
a) Get the necessary changes flowed through into qt5.git so we can
pick them up (the existing process is painfully slow)
b) Get their CI system to check for ASAN issues.

>
> Cheers
> Martin

Regards,
Ben
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Martin Graesslin]

On Saturday, April 23, 2016 8:48:17 PM CEST Ben Cooksley wrote:
> On Sat, Apr 23, 2016 at 8:35 PM, Martin Graesslin  
wrote:
> > On Saturday, April 23, 2016 1:09:00 PM CEST Ben Cooksley wrote:
> >> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  wrote:
> >> > On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
> >> >> On Fri, Apr 22, 2016 at 11:11 PM, David Faure  wrote:
> >> >> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
> >> >> >> GENERAL INFO
> >> >> >> 
> >> >> >> BUILD UNSTABLE
> >> >> >> Build URL:
> >> >> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=L
> >> >> >> inu
> >> >> >> x,
> >> >> >> compiler=gcc/11/>
> >> >> > 
> >> >> > Wow, ASAN detected a real bug in Qt here.
> >> >> > 
> >> >> > Fixed in https://codereview.qt-project.org/156728
> >> >> 
> >> >> As this issue essentially breaks any test on the CI system that
> >> >> depends on Qt I suggest all developers affected by this indicate this
> >> >> on the relevant reviews.
> >> > 
> >> > Hey guys,
> >> 
> >> Hi David,
> >> 
> >> > any chance to get this patch into our Qt build on the CI since it has
> >> > been
> >> > integrated upstream now? As it affects all tests that interact with
> >> > DBus
> >> > it
> >> > would be nice to resolve this on the CI.
> >> 
> >> We'll need upstream to update qt5.git (I think that's still required
> >> for changes to fully flow through) I think.
> >> We could try to hack the patch in, but then we'll end up having to
> >> undo that in a few weeks time.
> > 
> > Could we disable that ASAN check please[1]? I have two of my projects
> > failing due to the DBus problem and one further failing due to a similar
> > problem in QQuickStyleItem [2]. It's nice that we find errors, but I
> > rather not have my tests fail due to errors in Qt.
> 
> That would just cover up the issue.

Yes it would and that's exactly what I want.

To me the CI is currently producing false positives. It started to break from 
one moment to the other. It costs time to look into why it started to fail. It 
means that till that problem is fixed in Qt I cannot trust the CI system. It 
results in nobody noticing real breakage, because the build is broken anyway.

Then there is the problem of responsibility: I look at the output, I have no 
idea why that thing is broken, I have no idea how to build a minimal example 
which would reproduce it, even less on how to fix it. That's just a really bad 
situation to have a CI which can be trusted.

In summary: I don't want spend time to investigate false positives. If an 
option results in false positives, I think that we should disable it.

Of course Qt should get those bugs fixed, but for that Qt should enable ASAN on 
their CI system. If we get libraries which are free of ASAN problems, then we 
can enable it on our side. But false positives are just bad.

Cheers
Martin

signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Ben Cooksley]

On Mon, Apr 25, 2016 at 10:36 AM, Albert Astals Cid  wrote:
> El dilluns, 25 d’abril de 2016, a les 9:05:58 CEST, Ben Cooksley va escriure:
>> On Sun, Apr 24, 2016 at 11:46 AM, Michael Pyne  wrote:
>> > On Sat, April 23, 2016 13:09:00 Ben Cooksley wrote:
>> >> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  wrote:
>> >> > any chance to get this patch into our Qt build on the CI since it has
>> >> > been
>> >> > integrated upstream now? As it affects all tests that interact with
>> >> > DBus
>> >> > it
>> >> > would be nice to resolve this on the CI.
>> >>
>> >> We'll need upstream to update qt5.git (I think that's still required
>> >> for changes to fully flow through) I think.
>> >> We could try to hack the patch in, but then we'll end up having to
>> >> undo that in a few weeks time.
>> >
>> > If we're talking about Qt commit 1b9d082b, that appears to already be in
>> > the 5.6 branch (though not dev). I'm not sure which the CI uses though,
>> > if it's not 5.6 or less then it is probably more work than its worth to
>> > try to downgrade (something I've run into too much myself).
>>
>> The CI system uses the 5.6 branch, from qt5.git.
>> I've now triggered a build, but as qt5.git hasn't been updated since
>> our last build I have no idea whether this will pull the relevant
>> commit in.
>
> Is there any special reason we inflict ourselves the pain of using qt5.git
> instead of the standalone repos?

Primarily to keep everything in sync, so others can reproduce the
version of Qt 5 we're using.
We could try to do everything repo by repo but it would be quite a bit
of time to setup.

Also, I'm not sure if Qt's build system is up to having each module in
it's own installation prefix (haven't tried though).

>
> Cheers,
>   Albert

Regards,
Ben

>
>>
>> > Regards,
>> >
>> >  - Michael Pyne
>>
>> Cheers,
>> Ben
>> ___
>> Kde-frameworks-devel mailing list
>> Kde-frameworks-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>
>
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Albert Astals Cid]

El dilluns, 25 d’abril de 2016, a les 9:05:58 CEST, Ben Cooksley va escriure:
> On Sun, Apr 24, 2016 at 11:46 AM, Michael Pyne  wrote:
> > On Sat, April 23, 2016 13:09:00 Ben Cooksley wrote:
> >> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  wrote:
> >> > any chance to get this patch into our Qt build on the CI since it has
> >> > been
> >> > integrated upstream now? As it affects all tests that interact with
> >> > DBus
> >> > it
> >> > would be nice to resolve this on the CI.
> >> 
> >> We'll need upstream to update qt5.git (I think that's still required
> >> for changes to fully flow through) I think.
> >> We could try to hack the patch in, but then we'll end up having to
> >> undo that in a few weeks time.
> > 
> > If we're talking about Qt commit 1b9d082b, that appears to already be in
> > the 5.6 branch (though not dev). I'm not sure which the CI uses though,
> > if it's not 5.6 or less then it is probably more work than its worth to
> > try to downgrade (something I've run into too much myself).
> 
> The CI system uses the 5.6 branch, from qt5.git.
> I've now triggered a build, but as qt5.git hasn't been updated since
> our last build I have no idea whether this will pull the relevant
> commit in.

Is there any special reason we inflict ourselves the pain of using qt5.git 
instead of the standalone repos?

Cheers,
  Albert

> 
> > Regards,
> > 
> >  - Michael Pyne
> 
> Cheers,
> Ben
> ___
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel


___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Ben Cooksley]

On Sun, Apr 24, 2016 at 11:46 AM, Michael Pyne  wrote:
> On Sat, April 23, 2016 13:09:00 Ben Cooksley wrote:
>> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  wrote:
>> > any chance to get this patch into our Qt build on the CI since it has been
>> > integrated upstream now? As it affects all tests that interact with DBus
>> > it
>> > would be nice to resolve this on the CI.
>>
>> We'll need upstream to update qt5.git (I think that's still required
>> for changes to fully flow through) I think.
>> We could try to hack the patch in, but then we'll end up having to
>> undo that in a few weeks time.
>
> If we're talking about Qt commit 1b9d082b, that appears to already be in the
> 5.6 branch (though not dev). I'm not sure which the CI uses though, if it's
> not 5.6 or less then it is probably more work than its worth to try to
> downgrade (something I've run into too much myself).

The CI system uses the 5.6 branch, from qt5.git.
I've now triggered a build, but as qt5.git hasn't been updated since
our last build I have no idea whether this will pull the relevant
commit in.

>
> Regards,
>  - Michael Pyne

Cheers,
Ben
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Michael Pyne]

On Sat, April 23, 2016 13:09:00 Ben Cooksley wrote:
> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  wrote:
> > any chance to get this patch into our Qt build on the CI since it has been
> > integrated upstream now? As it affects all tests that interact with DBus
> > it
> > would be nice to resolve this on the CI.
> 
> We'll need upstream to update qt5.git (I think that's still required
> for changes to fully flow through) I think.
> We could try to hack the patch in, but then we'll end up having to
> undo that in a few weeks time.

If we're talking about Qt commit 1b9d082b, that appears to already be in the 
5.6 branch (though not dev). I'm not sure which the CI uses though, if it's 
not 5.6 or less then it is probably more work than its worth to try to 
downgrade (something I've run into too much myself).

Regards,
 - Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Ben Cooksley]

On Sat, Apr 23, 2016 at 8:35 PM, Martin Graesslin  wrote:
> On Saturday, April 23, 2016 1:09:00 PM CEST Ben Cooksley wrote:
>> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  wrote:
>> > On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
>> >> On Fri, Apr 22, 2016 at 11:11 PM, David Faure  wrote:
>> >> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
>> >> >> GENERAL INFO
>> >> >>
>> >> >> BUILD UNSTABLE
>> >> >> Build URL:
>> >> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=Linu
>> >> >> x,
>> >> >> compiler=gcc/11/>
>> >> >
>> >> > Wow, ASAN detected a real bug in Qt here.
>> >> >
>> >> > Fixed in https://codereview.qt-project.org/156728
>> >>
>> >> As this issue essentially breaks any test on the CI system that
>> >> depends on Qt I suggest all developers affected by this indicate this
>> >> on the relevant reviews.
>> >
>> > Hey guys,
>>
>> Hi David,
>>
>> > any chance to get this patch into our Qt build on the CI since it has been
>> > integrated upstream now? As it affects all tests that interact with DBus
>> > it
>> > would be nice to resolve this on the CI.
>>
>> We'll need upstream to update qt5.git (I think that's still required
>> for changes to fully flow through) I think.
>> We could try to hack the patch in, but then we'll end up having to
>> undo that in a few weeks time.
>
> Could we disable that ASAN check please[1]? I have two of my projects failing
> due to the DBus problem and one further failing due to a similar problem in
> QQuickStyleItem [2]. It's nice that we find errors, but I rather not have my
> tests fail due to errors in Qt.

That would just cover up the issue.
Also, it isn't that simple, as we already export ASAN_OPTIONS with a
different value, and changing that will break quite a lot more.

If QQuickStyleItem is broken as well, then the Qt developers need to
be asked to fix that as well then.

If it is that much of an issue, I suggest we simply do away with ASAN
testing altogether, as if our upstreams aren't going to bother with
it, it makes it pointless for us.

>
> Cheers
> Martin

Regards,
Ben

>
> [1] just export ASAN_OPTIONS=new_delete_type_mismatch=0
> [2] https://build.kde.org/user/graesslin/my-views/view/mgraesslin
> %20maintained/job/plasma-integration%20master%20kf5-qt5/
> PLATFORM=Linux,compiler=gcc/lastCompletedBuild/testReport/%28root%29/
> TestSuite/frameworkintegration_kfiledialogqml_unittest/
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Martin Graesslin]

On Saturday, April 23, 2016 1:09:00 PM CEST Ben Cooksley wrote:
> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  wrote:
> > On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
> >> On Fri, Apr 22, 2016 at 11:11 PM, David Faure  wrote:
> >> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
> >> >> GENERAL INFO
> >> >> 
> >> >> BUILD UNSTABLE
> >> >> Build URL:
> >> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=Linu
> >> >> x,
> >> >> compiler=gcc/11/>
> >> > 
> >> > Wow, ASAN detected a real bug in Qt here.
> >> > 
> >> > Fixed in https://codereview.qt-project.org/156728
> >> 
> >> As this issue essentially breaks any test on the CI system that
> >> depends on Qt I suggest all developers affected by this indicate this
> >> on the relevant reviews.
> > 
> > Hey guys,
> 
> Hi David,
> 
> > any chance to get this patch into our Qt build on the CI since it has been
> > integrated upstream now? As it affects all tests that interact with DBus
> > it
> > would be nice to resolve this on the CI.
> 
> We'll need upstream to update qt5.git (I think that's still required
> for changes to fully flow through) I think.
> We could try to hack the patch in, but then we'll end up having to
> undo that in a few weeks time.

Could we disable that ASAN check please[1]? I have two of my projects failing 
due to the DBus problem and one further failing due to a similar problem in 
QQuickStyleItem [2]. It's nice that we find errors, but I rather not have my 
tests fail due to errors in Qt.

Cheers
Martin

[1] just export ASAN_OPTIONS=new_delete_type_mismatch=0
[2] https://build.kde.org/user/graesslin/my-views/view/mgraesslin
%20maintained/job/plasma-integration%20master%20kf5-qt5/
PLATFORM=Linux,compiler=gcc/lastCompletedBuild/testReport/%28root%29/
TestSuite/frameworkintegration_kfiledialogqml_unittest/


signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Ben Cooksley]

On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil  wrote:
> On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
>> On Fri, Apr 22, 2016 at 11:11 PM, David Faure  wrote:
>> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
>> >> GENERAL INFO
>> >>
>> >> BUILD UNSTABLE
>> >> Build URL:
>> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=Linux,
>> >> compiler=gcc/11/>
>> > Wow, ASAN detected a real bug in Qt here.
>> >
>> > Fixed in https://codereview.qt-project.org/156728
>>
>> As this issue essentially breaks any test on the CI system that
>> depends on Qt I suggest all developers affected by this indicate this
>> on the relevant reviews.
>
> Hey guys,

Hi David,

>
> any chance to get this patch into our Qt build on the CI since it has been
> integrated upstream now? As it affects all tests that interact with DBus it
> would be nice to resolve this on the CI.

We'll need upstream to update qt5.git (I think that's still required
for changes to fully flow through) I think.
We could try to hack the patch in, but then we'll end up having to
undo that in a few weeks time.

>
> Thanks
> Dan
>

Cheers,
Ben

>>
>> Cheers,
>> Ben
>>
>> > --
>> > David Faure, fa...@kde.org, http://www.davidfaure.fr
>> > Working on KDE Frameworks 5
>> >
>> > ___
>> > Kde-frameworks-devel mailing list
>> > Kde-frameworks-devel@kde.org
>> > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>>
>> ___
>> Kde-frameworks-devel mailing list
>> Kde-frameworks-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>
>
> --
> Daniel Vrátil
> www.dvratil.cz | dvra...@kde.org
> IRC: dvratil on Freenode (#kde, #kontact, #akonadi, #fedora-kde)
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Daniel Vrátil]

On Saturday, April 23, 2016 1:44:16 AM CEST Ben Cooksley wrote:
> On Fri, Apr 22, 2016 at 11:11 PM, David Faure  wrote:
> > On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
> >> GENERAL INFO
> >> 
> >> BUILD UNSTABLE
> >> Build URL:
> >> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=Linux,
> >> compiler=gcc/11/> 
> > Wow, ASAN detected a real bug in Qt here.
> > 
> > Fixed in https://codereview.qt-project.org/156728
> 
> As this issue essentially breaks any test on the CI system that
> depends on Qt I suggest all developers affected by this indicate this
> on the relevant reviews.

Hey guys,

any chance to get this patch into our Qt build on the CI since it has been 
integrated upstream now? As it affects all tests that interact with DBus it 
would be nice to resolve this on the CI.

Thanks
Dan

> 
> Cheers,
> Ben
> 
> > --
> > David Faure, fa...@kde.org, http://www.davidfaure.fr
> > Working on KDE Frameworks 5
> > 
> > ___
> > Kde-frameworks-devel mailing list
> > Kde-frameworks-devel@kde.org
> > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
> 
> ___
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel


-- 
Daniel Vrátil
www.dvratil.cz | dvra...@kde.org
IRC: dvratil on Freenode (#kde, #kontact, #akonadi, #fedora-kde)

signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[Ben Cooksley]

On Fri, Apr 22, 2016 at 11:11 PM, David Faure  wrote:
> On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
>>
>> GENERAL INFO
>>
>> BUILD UNSTABLE
>> Build URL: 
>> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/11/
>
> Wow, ASAN detected a real bug in Qt here.
>
> Fixed in https://codereview.qt-project.org/156728

As this issue essentially breaks any test on the CI system that
depends on Qt I suggest all developers affected by this indicate this
on the relevant reviews.

Cheers,
Ben

>
> --
> David Faure, fa...@kde.org, http://www.davidfaure.fr
> Working on KDE Frameworks 5
>
> ___
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Re: Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux, gcc - Build # 11 - Still Unstable!

[David Faure]

On Thursday 21 April 2016 14:57:52 no-re...@kde.org wrote:
> 
> GENERAL INFO
> 
> BUILD UNSTABLE
> Build URL: 
> https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/11/

Wow, ASAN detected a real bug in Qt here.

Fixed in https://codereview.qt-project.org/156728

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5

___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Jenkins-kde-ci: kdbusaddons master kf5-qt5 » Linux,gcc - Build # 11 - Still Unstable!

[no-reply]

GENERAL INFO

BUILD UNSTABLE
Build URL: 
https://build.kde.org/job/kdbusaddons%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/11/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Thu, 21 Apr 2016 14:42:33 +
Build duration: 56 sec

CHANGE SET
No changes


JUNIT RESULTS

Name: (root) Failed: 1 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 2 
test(s)Failed: TestSuite.kdbusservicetest

COBERTURA RESULTS

Cobertura Coverage Report
  PACKAGES 2/2 (100%)FILES 3/6 (50%)CLASSES 3/6 (50%)LINE 94/264 
(36%)CONDITIONAL 14/124 (11%)

By packages
  
autotests
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 61/62 (98%)CONDITIONAL 
8/12 (67%)
src
FILES 2/5 (40%)CLASSES 2/5 (40%)LINE 33/202 (16%)CONDITIONAL 
6/112 (5%)___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel