[Buildroot] [autobuild.buildroot.net] Build results for 2018-05-31

[Buildroot] [autobuild.buildroot.net] Build results for 2018-05-31

[Thomas Petazzoni]

Hello,

Build statistics for 2018-05-31
===============================

      branch |  OK | NOK | TIM | TOT |
   2018.02.x |  17 |   4 |   0 |  21 |
      master | 146 |   6 |   1 | 153 |
        next |  29 |  16 |   0 |  45 |

Results for branch '2018.02.x'
==============================

Classification of failures by reason
------------------------------------

                   exim-4.89.1 | 1 
          host-faketime-v0.9.6 | 1 
                   libnss-3.33 | 1 
                  samba4-4.7.6 | 1 


Detail of failures
------------------

      x86_64 |                    exim-4.89.1 | NOK | http://autobuild.buildroot.net/results/621fff14b549352ba46fd750d769450d180885ee |     
         arm |           host-faketime-v0.9.6 | NOK | http://autobuild.buildroot.net/results/8f185a3772f12f442787dd37f5aed300b12a311c | ORPH
   powerpc64 |                    libnss-3.33 | NOK | http://autobuild.buildroot.net/results/014aac80efe59a38a74fe80c6144d56d8b2f5e6f |     
    mips64el |                   samba4-4.7.6 | NOK | http://autobuild.buildroot.net/results/3623bbcac203ff30c0be6bd39a63cdeb18026b4f |     

Results for branch 'master'
===========================

Classification of failures by reason
------------------------------------

                      qt-4.8.7 | 2 
                dos2unix-7.4.0 | 1 
                 expect-5.45.3 | 1 
                    links-2.14 | 1 
openvmtools-5a9033ddfa95786... | 1 
                       unknown | 1 


Detail of failures
------------------

         arm |                 dos2unix-7.4.0 | NOK | http://autobuild.buildroot.net/results/ebfe81e65751d7a5ca3aa4e20cc708a24ba65204 |     
   powerpc64 |                  expect-5.45.3 | NOK | http://autobuild.buildroot.net/results/dd29953f28577674070717cbb5feba8e12aad8e3 | ORPH
      x86_64 |                     links-2.14 | NOK | http://autobuild.buildroot.net/results/57d2bebaa430d17eac06f1736d17c73d0b3732b4 | ORPH
      x86_64 | openvmtools-5a9033ddfa95786... | NOK | http://autobuild.buildroot.net/results/f2c73480b5a1060bb17ac260ef82c3e641fad085 |     
     powerpc |                       qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/360d6b26249dac494207ce7c44e34e88ff0d39fc | ORPH
     powerpc |                       qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/cebd1d3d013d40bf71bf20696c28818f58d9533a | ORPH
      xtensa |                        unknown | TIM | http://autobuild.buildroot.net/results/1c237d9f8de88893b7094e0af9885d21d55e8446 |     

Results for branch 'next'
=========================

Classification of failures by reason
------------------------------------

                   libnss-3.37 | 4 
host-imx-mkimage-rel_imx_4.... | 3 
              librtlsdr-v0.5.4 | 3 
                protobuf-3.5.1 | 2 
          host-faketime-v0.9.6 | 1 
               host-llvm-5.0.1 | 1 
         perl-libwww-perl-6.33 | 1 
                   systemd-237 | 1 


Detail of failures
------------------

    mips64el |           host-faketime-v0.9.6 | NOK | http://autobuild.buildroot.net/results/c95c82e22a13bad55e4e67beff1aa527770c1844 | ORPH
        m68k | host-imx-mkimage-rel_imx_4.... | NOK | http://autobuild.buildroot.net/results/0af94c6ad7a956c7db35eee3074927b6866bc1b3 |     
         arm | host-imx-mkimage-rel_imx_4.... | NOK | http://autobuild.buildroot.net/results/afab0f9496f536bdb1f42dfb183c2bbd25d4cf2b |     
    mips64el | host-imx-mkimage-rel_imx_4.... | NOK | http://autobuild.buildroot.net/results/2cdd8e2f5263745f83e998548d1eff990d429f02 |     
      x86_64 |                host-llvm-5.0.1 | NOK | http://autobuild.buildroot.net/results/84fdc019ac2f3010c810f144a9949a8b1863b5d4 |     
      mipsel |                    libnss-3.37 | NOK | http://autobuild.buildroot.net/results/89298001e58c6a20b4fe45f7d0d6b3e14df3e09e |     
         arm |                    libnss-3.37 | NOK | http://autobuild.buildroot.net/results/d92a2336e9ca76047cea6e4c5650e4f00e9e4f99 |     
         arm |                    libnss-3.37 | NOK | http://autobuild.buildroot.net/results/18651c3f6cca288d3ae744020ced71be7a172097 |     
         arm |                    libnss-3.37 | NOK | http://autobuild.buildroot.net/results/59cdc81460228a50b01445cbc8ebef04a08b117b |     
        m68k |               librtlsdr-v0.5.4 | NOK | http://autobuild.buildroot.net/results/ddbe791a8749d865eb0abe882f816807971ae829 |     
         arm |               librtlsdr-v0.5.4 | NOK | http://autobuild.buildroot.net/results/ff86557b6e4e43894406a2dd0da45f3176423850 |     
         arm |               librtlsdr-v0.5.4 | NOK | http://autobuild.buildroot.net/results/aafbc679f9db3efb75623f24ffce05148f343e60 |     
 powerpc64le |          perl-libwww-perl-6.33 | NOK | http://autobuild.buildroot.net/results/6f7745010ca589876a24d522bc0cb4a0dca26768 |     
     sparc64 |                 protobuf-3.5.1 | NOK | http://autobuild.buildroot.net/results/5480a6087a5a782505cec88f797116d8679df3ac |     
     sparc64 |                 protobuf-3.5.1 | NOK | http://autobuild.buildroot.net/results/982f727495c1d3524685015c34b1cbb1e0bbb4b0 |     
     powerpc |                    systemd-237 | NOK | http://autobuild.buildroot.net/results/b8f5d663412f369590697bd278aa4d871200db79 |     


-- 
http://autobuild.buildroot.net

[Buildroot] qt-4.8.7 ICE on powerpc [was: [autobuild.buildroot.net] Build results for 2018-05-31]

[Arnout Vandecappelle]

On 01-06-18 08:00, Thomas Petazzoni wrote:
>      powerpc |                       qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/cebd1d3d013d40bf71bf20696c28818f58d9533a | ORPH

 This one has also been failing for a *long* time. It is caused by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60818

 Should we introduce a BR2_TOOLCHAIN_HAS_GCC_BUG_60818 here? However, AFAICS
it's only Qt4 that is failing, so maybe an autobuild exclusion is more
appropriate in this case.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] qt-4.8.7 ICE on powerpc [was: [autobuild.buildroot.net] Build results for 2018-05-31]

[Thomas Petazzoni]

Hello,

On Fri, 1 Jun 2018 09:58:01 +0200, Arnout Vandecappelle wrote:
> On 01-06-18 08:00, Thomas Petazzoni wrote:
> >      powerpc |                       qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/cebd1d3d013d40bf71bf20696c28818f58d9533a | ORPH  
> 
>  This one has also been failing for a *long* time. It is caused by
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60818

Doesn't this bug report claims that the issue has been fixed in gcc
6.x... but still the autobuild failure happens with a gcc 6.x based
toolchain ?

>  Should we introduce a BR2_TOOLCHAIN_HAS_GCC_BUG_60818 here? However, AFAICS
> it's only Qt4 that is failing, so maybe an autobuild exclusion is more
> appropriate in this case.

I continue to prefer the BR2_TOOLCHAIN_HAS_GCC_BUG_xyz approach. There
are only two packages that select BR2_PACKAGE_QT, and those packages in
turn don't have any reverse dependencies. So it's not a big deal to
propagate a BR2_TOOLCHAIN_HAS_GCC_BUG_xyz option.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] qt-4.8.7 ICE on powerpc [was: [autobuild.buildroot.net] Build results for 2018-05-31]

[Arnout Vandecappelle]

On 01-06-18 11:06, Thomas Petazzoni wrote:
> Hello,
> 
> On Fri, 1 Jun 2018 09:58:01 +0200, Arnout Vandecappelle wrote:
>> On 01-06-18 08:00, Thomas Petazzoni wrote:
>>>      powerpc |                       qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/cebd1d3d013d40bf71bf20696c28818f58d9533a | ORPH  
>>
>>  This one has also been failing for a *long* time. It is caused by
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60818
> 
> Doesn't this bug report claims that the issue has been fixed in gcc
> 6.x... but still the autobuild failure happens with a gcc 6.x based
> toolchain ?

 Well, a single bug report sometimes contains multiple bugs :-). Apparently part
of the problem was only fixed in GCC7.2, and it's possible that some part is not
fixed yet.


 Regards,
 Arnout

> 
>>  Should we introduce a BR2_TOOLCHAIN_HAS_GCC_BUG_60818 here? However, AFAICS
>> it's only Qt4 that is failing, so maybe an autobuild exclusion is more
>> appropriate in this case.
> 
> I continue to prefer the BR2_TOOLCHAIN_HAS_GCC_BUG_xyz approach. There
> are only two packages that select BR2_PACKAGE_QT, and those packages in
> turn don't have any reverse dependencies. So it's not a big deal to
> propagate a BR2_TOOLCHAIN_HAS_GCC_BUG_xyz option.
> 
> Best regards,
> 
> Thomas
> 

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] qt-4.8.7 ICE on powerpc [was: [autobuild.buildroot.net] Build results for 2018-05-31]

[Thomas Petazzoni]

Hello,

On Fri, 1 Jun 2018 13:12:56 +0200, Arnout Vandecappelle wrote:

> > On Fri, 1 Jun 2018 09:58:01 +0200, Arnout Vandecappelle wrote:  
> >> On 01-06-18 08:00, Thomas Petazzoni wrote:  
> >>>      powerpc |                       qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/cebd1d3d013d40bf71bf20696c28818f58d9533a | ORPH    
> >>
> >>  This one has also been failing for a *long* time. It is caused by
> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60818  
> > 
> > Doesn't this bug report claims that the issue has been fixed in gcc
> > 6.x... but still the autobuild failure happens with a gcc 6.x based
> > toolchain ?  
> 
>  Well, a single bug report sometimes contains multiple bugs :-). Apparently part
> of the problem was only fixed in GCC7.2, and it's possible that some part is not
> fixed yet.

If a single bug report contains multiple bugs, then our
BR2_TOOLCHAIN_GCC_HAS_BUG_xyz naming has a serious problem :-)

Is this specific Qt4 issue resolved with gcc 7.x ? Some testing on this
would be nice.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [autobuild.buildroot.net] Build results for 2018-05-31

[Matthew Weber]

On Fri, Jun 1, 2018 at 1:00 AM, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> Build statistics for 2018-05-31
> ===============================

> Results for branch 'next'
> =========================
>

>      sparc64 |                 protobuf-3.5.1 | NOK | http://autobuild.buildroot.net/results/5480a6087a5a782505cec88f797116d8679df3ac |
>      sparc64 |                 protobuf-3.5.1 | NOK | http://autobuild.buildroot.net/results/982f727495c1d3524685015c34b1cbb1e0bbb4b0 |

Looks like a known issue and has been patched on the master branch. I
left a note on the pull request asking about plans for the 3.5.1.x
release.  https://github.com/google/protobuf/pull/3955

Matt

[Buildroot] [autobuild.buildroot.net] Build results for 2018-05-31

[Thomas Petazzoni]

Hello,

On Fri, 1 Jun 2018 07:48:35 -0500, Matthew Weber wrote:

> >      sparc64 |                 protobuf-3.5.1 | NOK | http://autobuild.buildroot.net/results/5480a6087a5a782505cec88f797116d8679df3ac |
> >      sparc64 |                 protobuf-3.5.1 | NOK | http://autobuild.buildroot.net/results/982f727495c1d3524685015c34b1cbb1e0bbb4b0 |  
> 
> Looks like a known issue and has been patched on the master branch. I
> left a note on the pull request asking about plans for the 3.5.1.x
> release.  https://github.com/google/protobuf/pull/3955

Well, why don't we simply backport this patch ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [autobuild.buildroot.net] Build results for 2018-05-31

[Matthew Weber]

Thomas,

On Fri, Jun 1, 2018 at 7:57 AM, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> On Fri, 1 Jun 2018 07:48:35 -0500, Matthew Weber wrote:
>
>> >      sparc64 |                 protobuf-3.5.1 | NOK | http://autobuild.buildroot.net/results/5480a6087a5a782505cec88f797116d8679df3ac |
>> >      sparc64 |                 protobuf-3.5.1 | NOK | http://autobuild.buildroot.net/results/982f727495c1d3524685015c34b1cbb1e0bbb4b0 |
>>
>> Looks like a known issue and has been patched on the master branch. I
>> left a note on the pull request asking about plans for the 3.5.1.x
>> release.  https://github.com/google/protobuf/pull/3955
>
> Well, why don't we simply backport this patch ?
>

Definitely can, was just waiting to see if they had a response before I started.

Matt

[Buildroot] qt-4.8.7 ICE on powerpc [was: [autobuild.buildroot.net] Build results for 2018-05-31]

[Arnout Vandecappelle]

On 01-06-18 14:24, Thomas Petazzoni wrote:
> Hello,
> 
> On Fri, 1 Jun 2018 13:12:56 +0200, Arnout Vandecappelle wrote:
> 
>>> On Fri, 1 Jun 2018 09:58:01 +0200, Arnout Vandecappelle wrote:  
>>>> On 01-06-18 08:00, Thomas Petazzoni wrote:  
>>>>>      powerpc |                       qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/cebd1d3d013d40bf71bf20696c28818f58d9533a | ORPH    
>>>>
>>>>  This one has also been failing for a *long* time. It is caused by
>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60818  
>>>
>>> Doesn't this bug report claims that the issue has been fixed in gcc
>>> 6.x... but still the autobuild failure happens with a gcc 6.x based
>>> toolchain ?  
>>
>>  Well, a single bug report sometimes contains multiple bugs :-). Apparently part
>> of the problem was only fixed in GCC7.2, and it's possible that some part is not
>> fixed yet.
> 
> If a single bug report contains multiple bugs, then our
> BR2_TOOLCHAIN_GCC_HAS_BUG_xyz naming has a serious problem :-)
> 
> Is this specific Qt4 issue resolved with gcc 7.x ? Some testing on this
> would be nice.

 Since this is about Qt4 which is EOL since 3 years, perhaps we can just exclude
Qt4 entirely for powerpc? I think powerpc with UI is rather rare anyway...

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] qt-4.8.7 ICE on powerpc [was: [autobuild.buildroot.net] Build results for 2018-05-31]

[Peter Korsgaard]

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

 >> If a single bug report contains multiple bugs, then our
 >> BR2_TOOLCHAIN_GCC_HAS_BUG_xyz naming has a serious problem :-)
 >> 
 >> Is this specific Qt4 issue resolved with gcc 7.x ? Some testing on this
 >> would be nice.

 >  Since this is about Qt4 which is EOL since 3 years, perhaps we can just exclude
 > Qt4 entirely for powerpc? I think powerpc with UI is rather rare anyway...

Or perhaps simply get rid of Qt4? It is still available in 2018.02.x,
and we should probably get rid of it before 2019.02.

-- 
Bye, Peter Korsgaard