[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Thomas Petazzoni]

Hello,

Build statistics for 2019-05-12
===============================

      branch |  OK | NOK | TIM | TOT |
   2019.02.x |  30 |   1 |   0 |  31 |
      master | 177 |  11 |   5 | 193 |

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

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

                mono-5.20.1.27 | 2 
                       netsurf | 2 
                          atop | 1 
                     gdb-8.1.1 | 1 
                        glibmm | 1 
                host-libsodium | 1 
                      iwd-0.13 | 1 
                  linuxptp-2.0 | 1 
                   netsurf-3.8 | 1 
                  rpm-4.14.2.1 | 1 
              spandsp-20180108 | 1 
           tesseract-ocr-4.0.0 | 1 
                   whois-5.4.0 | 1 
          wpebackend-fdo-1.0.1 | 1 


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

microblazeel |                           atop | TIM | http://autobuild.buildroot.net/results/94aa00f776b8a3491ac0b3212c95f5e666c5a29a |     
         arm |                      gdb-8.1.1 | NOK | http://autobuild.buildroot.net/results/a81eb395bd95306fcbb07c1443c9134fd63fa379 | ORPH
microblazeel |                         glibmm | TIM | http://autobuild.buildroot.net/results/e196d77626b877dc3454d21febe20a04877c02a9 |     
 powerpc64le |                 host-libsodium | TIM | http://autobuild.buildroot.net/results/30bcf2ab8f95574b20ac2833ce237b3a885c01b8 |     
      mipsel |                       iwd-0.13 | NOK | http://autobuild.buildroot.net/results/176a40dd27ad92e5ad07eabbacdddf4e95edcba7 |     
     aarch64 |                   linuxptp-2.0 | NOK | http://autobuild.buildroot.net/results/3896b76ea6494222e062369e537a76da577f502e |     
         arm |                 mono-5.20.1.27 | NOK | http://autobuild.buildroot.net/results/ee6d037154127cc6572f06e9a78bae383ea381bc |     
         arm |                 mono-5.20.1.27 | NOK | http://autobuild.buildroot.net/results/e505ec5aed040b34754d75e91f9de7ca334f2da9 |     
      mipsel |                        netsurf | TIM | http://autobuild.buildroot.net/results/b454b00198ddd6601b2238f9c1d0bb2154c1901e |     
     riscv64 |                        netsurf | TIM | http://autobuild.buildroot.net/results/fc1ffc5c3a006f66b11de0e0127e4224aec1aa2d |     
     powerpc |                    netsurf-3.8 | NOK | http://autobuild.buildroot.net/results/04ac3da1d9584095f57f3ea07de73e06449618d8 |     
     powerpc |                   rpm-4.14.2.1 | NOK | http://autobuild.buildroot.net/results/a1446b419f5f59f65fe80849182e38457de203b5 |     
        i686 |               spandsp-20180108 | NOK | http://autobuild.buildroot.net/results/674ef1b8791c7f9dbdf4e7a0f84192abb59c21ae |     
      mipsel |            tesseract-ocr-4.0.0 | NOK | http://autobuild.buildroot.net/results/dba4cf210815c66aac5474fbc05f418a2cc98bf6 |     
     aarch64 |                    whois-5.4.0 | NOK | http://autobuild.buildroot.net/results/d272b906cc0a1dcced2b8d48aad77b272300005a |     
         arm |           wpebackend-fdo-1.0.1 | NOK | http://autobuild.buildroot.net/results/07dded285364ca342c3270ba71bdc8ef72e1db26 |     

Results for branch '2019.02.x'
==============================

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

                   netsurf-3.8 | 1 


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

        m68k |                    netsurf-3.8 | NOK | http://autobuild.buildroot.net/results/a2097f0bf03d8409164cc8ad6dba6775c49d3f91 |     


-- 
http://autobuild.buildroot.net

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Thomas Petazzoni]

Hello,

Giulio, Matt, Vadym, Gilles, Peter, Adrian, there are some
questions/topics/issues for you below!

On Mon, 13 May 2019 06:00:37 -0000
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

>       branch |  OK | NOK | TIM | TOT |
>    2019.02.x |  30 |   1 |   0 |  31 |
>       master | 177 |  11 |   5 | 193 |

Results are not too bad, but we have a fairly high number of timeouts,
which is not nice. Let's have a look at the details.

> microblazeel |                           atop | TIM | http://autobuild.buildroot.net/results/94aa00f776b8a3491ac0b3212c95f5e666c5a29a |     

This seems weird. Happened when linking a fairly simple application,
never had another timeout on that package.

Giulio, could you try to re-run the exact same defconfig (using
br-reproduce-build) and see if it's reproducible ?

>          arm |                      gdb-8.1.1 | NOK | http://autobuild.buildroot.net/results/a81eb395bd95306fcbb07c1443c9134fd63fa379 | ORPH

This would be fixed by http://patchwork.ozlabs.org/patch/1098520/.

> microblazeel |                         glibmm | TIM | http://autobuild.buildroot.net/results/e196d77626b877dc3454d21febe20a04877c02a9 |     

Another weird timeout, this time on Matt's autobuilder. Matt, could you
have a look ?

But this seems to happen quite regularly, even on other autobuilder
machines:

  http://autobuild.buildroot.net/?reason=glibmm

Always on microblazeel, like the timeout on "atop" discussed above. I
guess that probably points at a compiler issue, which means it should
be reproducible.

>  powerpc64le |                 host-libsodium | TIM | http://autobuild.buildroot.net/results/30bcf2ab8f95574b20ac2833ce237b3a885c01b8 |     

The usual host-libsodium timeout on Julien's machine, there is a
separate thread of discussion about it.

>       mipsel |                       iwd-0.13 | NOK | http://autobuild.buildroot.net/results/176a40dd27ad92e5ad07eabbacdddf4e95edcba7 |     

/data/buildroot/buildroot-test/instance-1/output/host/bin/autoconf: line 442: /usr/bin/sed: No such file or directory
/data/buildroot/buildroot-test/instance-1/output/host/bin/autoconf: line 405: /usr/bin/expr: No such file or directory
/data/buildroot/buildroot-test/instance-1/output/host/bin/autoconf: line 407: /usr/bin/expr: No such file or directory
/data/buildroot/buildroot-test/instance-1/output/host/bin/autoconf: line 442: /usr/bin/sed: No such file or directory
/data/buildroot/buildroot-test/instance-1/output/host/bin/autoconf: line 442: printf: write error: Broken pipe
[...]
expr: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
sed: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/data/buildroot/buildroot-test/instance-1/output/host/bin/autoconf: line 442: printf: write error: Broken pipe
expr: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

Wow, this looks like a system/distro issue.

Xogium, did you do any system update around the time of this build
failure ? Could you have a look ?

>      aarch64 |                   linuxptp-2.0 | NOK | http://autobuild.buildroot.net/results/3896b76ea6494222e062369e537a76da577f502e |   

Would be fixed by http://patchwork.ozlabs.org/patch/1047538/.
  
>          arm |                 mono-5.20.1.27 | NOK | http://autobuild.buildroot.net/results/ee6d037154127cc6572f06e9a78bae383ea381bc |     
>          arm |                 mono-5.20.1.27 | NOK | http://autobuild.buildroot.net/results/e505ec5aed040b34754d75e91f9de7ca334f2da9 |     

Would be fixed by http://patchwork.ozlabs.org/patch/1098523/.

>       mipsel |                        netsurf | TIM | http://autobuild.buildroot.net/results/b454b00198ddd6601b2238f9c1d0bb2154c1901e |     
>      riscv64 |                        netsurf | TIM | http://autobuild.buildroot.net/results/fc1ffc5c3a006f66b11de0e0127e4224aec1aa2d |     

Would be fixed by my netsurf patch series.

>      powerpc |                    netsurf-3.8 | NOK | http://autobuild.buildroot.net/results/04ac3da1d9584095f57f3ea07de73e06449618d8 |     

Ditto.

>      powerpc |                   rpm-4.14.2.1 | NOK | http://autobuild.buildroot.net/results/a1446b419f5f59f65fe80849182e38457de203b5 |     

Some libintl dance missing. Vadim ?

>         i686 |               spandsp-20180108 | NOK | http://autobuild.buildroot.net/results/674ef1b8791c7f9dbdf4e7a0f84192abb59c21ae |     

gsm0610_rpe.c:132:5: error: invalid 'asm': invalid constraints for operand

Bernd ?

>       mipsel |            tesseract-ocr-4.0.0 | NOK | http://autobuild.buildroot.net/results/dba4cf210815c66aac5474fbc05f418a2cc98bf6 |     

ERROR: fra.traineddata has wrong sha256 hash:
ERROR: expected: eac01c1d72540d6090facb7b2f42dd0a2ee8fc57c5be1b20548ae668e2761913
ERROR: got     : 86afb23ad146467f263e8ade56fd3951b1cc28f8c4eebc34f993d3c02d88a7ab
ERROR: Incomplete download, or man-in-the-middle (MITM) attack

Ah ah. Seems like sources.buildroot.net does not have the latest
version of the files. But in fact the issue is that the file names do
not contain the version... so obviously this is not going to work well.

I think our approach of downloading the tessdata files from the
tesseract-ocr package is not good. We probably need to have a separate
tessdata package, that downloads the entire dataset, so that we can
rely on proper version numbers.

Gilles: could you cook a patch to implement this ?

>      aarch64 |                    whois-5.4.0 | NOK | http://autobuild.buildroot.net/results/d272b906cc0a1dcced2b8d48aad77b272300005a |     

2019-05-12 13:20:06 ERROR 500: Internal Server Error.

on the Debian server + our mirror didn't had the tarball.

Peter, any idea why our mirror doesn't have the tarball ? The bump
dates back from January 2019, we should have mirrored the tarball since
then.

>          arm |           wpebackend-fdo-1.0.1 | NOK | http://autobuild.buildroot.net/results/07dded285364ca342c3270ba71bdc8ef72e1db26 |     

Should be fixed by http://patchwork.ozlabs.org/patch/1085508/, but we
still haven't received feedback from Adrian on this one.

> Results for branch '2019.02.x'
> ==============================
> 
> Classification of failures by reason
> ------------------------------------
> 
>                    netsurf-3.8 | 1 
> 
> 
> Detail of failures
> ------------------
> 
>         m68k |                    netsurf-3.8 | NOK | http://autobuild.buildroot.net/results/a2097f0bf03d8409164cc8ad6dba6775c49d3f91 |     

Same static linking issue, would be fixed by my patch series on netsurf.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Baruch Siach]

Hi Thomas,
  
On Mon, May 13, 2019 at 01:55:20PM +0200, Thomas Petazzoni wrote:
> >      powerpc |                   rpm-4.14.2.1 | NOK | http://autobuild.buildroot.net/results/a1446b419f5f59f65fe80849182e38457de203b5 |     
> 
> Some libintl dance missing. Vadim ?

Should be fixed by commit 653bf938372.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Giulio Benetti]

Hello Thomas,

Il 13/05/2019 13:55, Thomas Petazzoni ha scritto:
> Hello,
> 
> Giulio, Matt, Vadym, Gilles, Peter, Adrian, there are some
> questions/topics/issues for you below!
> 
> On Mon, 13 May 2019 06:00:37 -0000
> Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> 
>>        branch |  OK | NOK | TIM | TOT |
>>     2019.02.x |  30 |   1 |   0 |  31 |
>>        master | 177 |  11 |   5 | 193 |
> 
> Results are not too bad, but we have a fairly high number of timeouts,
> which is not nice. Let's have a look at the details.
> 
>> microblazeel |                           atop | TIM | http://autobuild.buildroot.net/results/94aa00f776b8a3491ac0b3212c95f5e666c5a29a |
> 
> This seems weird. Happened when linking a fairly simple application,
> never had another timeout on that package.
> 
> Giulio, could you try to re-run the exact same defconfig (using
> br-reproduce-build) and see if it's reproducible ?

Actually I'm experiencing timeout both on my pc and my server.
Launching htop I've found it hangs while:
/home/giuliobenetti/br_reproduce/94aa00f776b8a3491ac0b3212c95f5e666c5a29a/output/host/libexec/gcc/microblazeel-buildroot-linux-uclibc/7.4.0/cc1 
-quiet -isysroot 
/home/giuliobenetti/br_reproduce/94aa00f776b8a3491ac0b3212c95f5e666c5a29a/output/host/microblazeel-buildroot-linux-uclibc/sysroot 
-D _LARGEFILE_SOURCE -D _LARGEFILE64_SOURCE -D _FILE_OFFSET_BITS=64 -D 
_LARGEFILE_SOURCE -D _LARGEFILE64_SOURCE -D _FILE_OFFSET_BITS=64 
showgeneric.c -quiet -dumpbase showgeneric.c -auxbase-strip 
showgeneric.o -g2 -O2 -o /tmp/ccPqa6b0.s

With 1 core at 100%

Is there a way to understand why?

-- 
Giulio Benetti
CTO

MICRONOVA SRL
Sede: Via A. Niedda 3 - 35010 Vigonza (PD)
Tel. 049/8931563 - Fax 049/8931346
Cod.Fiscale - P.IVA 02663420285
Capitale Sociale ? 26.000 i.v.
Iscritta al Reg. Imprese di Padova N. 02663420285
Numero R.E.A. 258642

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

Hi,

 >> aarch64 |                    whois-5.4.0 | NOK | http://autobuild.buildroot.net/results/d272b906cc0a1dcced2b8d48aad77b272300005a |     

 > 2019-05-12 13:20:06 ERROR 500: Internal Server Error.

 > on the Debian server + our mirror didn't had the tarball.

 > Peter, any idea why our mirror doesn't have the tarball ? The bump
 > dates back from January 2019, we should have mirrored the tarball since
 > then.

Hmm, no - Not really. I thought it might be related to the
BR2_PACKAGE_BUSYBOX_SHOW_OTHERS dependency, but manually running make
whois-source did download it:

make whois-source
/usr/bin/make -j1 O=/home/jacmet/source/buildroot-mirror/output HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" syncconfig
>>> whois 5.4.0 Downloading
--2019-05-14 08:36:40--  http://snapshot.debian.org/archive/debian/20181026T220636Z/pool/main/w/whois/whois_5.4.0.tar.xz
Resolving snapshot.debian.org (snapshot.debian.org)... 193.62.202.27, 185.17.185.185, 2001:1af8:4020:b030:deb::185, ...
Connecting to snapshot.debian.org (snapshot.debian.org)|193.62.202.27|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 83576 (82K)
Saving to: ?/home/jacmet/source/buildroot-mirror/output/build/.whois_5.4.0.tar.xz.0Bh8tA/output?

100%[==============================================================================================================>] 83,576       197KB/s   in 0.4s

2019-05-14 08:36:41 (197 KB/s) - ?/home/jacmet/source/buildroot-mirror/output/build/.whois_5.4.0.tar.xz.0Bh8tA/output? saved [83576/83576]

whois_5.4.0.tar.xz: OK (sha256: 3775ae0cfaa6dd8d886e5233c4826225cddcb88c99c2a08130d14e15fe58e378)


And the logic does end up passing whois-source to make, so I am not
sure. Perhaps one of the new dependencies.sh checks fails?

We indeed do have:

commit dc5553d2ce1d333cbecac563d2c55525aa8e14ef
Author: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Date:   Tue Jun 5 20:13:47 2018 +0200

    dependencies.sh: add perl autodie for whois

    Add dependency on perl autodie if whois package is selected

And the s.b.o machine does not have autodie:

perl -e "require autodie"
Can't locate autodie.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at -e line 1.

But that only explains it for the part where we run

make allyespackageconfig && make source

Anyway, I have now manually downloaded it.

-- 
Bye, Peter Korsgaard

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Matthew Weber]

On Mon, May 13, 2019 at 6:55 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello,
>
> Giulio, Matt, Vadym, Gilles, Peter, Adrian, there are some
> questions/topics/issues for you below!
>

[snip]


> > microblazeel |                         glibmm | TIM | http://autobuild.buildroot.net/results/e196d77626b877dc3454d21febe20a04877c02a9 |
>
> Another weird timeout, this time on Matt's autobuilder. Matt, could you
> have a look ?
>
> But this seems to happen quite regularly, even on other autobuilder
> machines:
>
>   http://autobuild.buildroot.net/?reason=glibmm
>
> Always on microblazeel, like the timeout on "atop" discussed above. I
> guess that probably points at a compiler issue, which means it should
> be reproducible.
>

Build definitely hung (didn't even need to be on that build machine).
I'll hopefully get some time to take a deeper look later.

#74 0x00000000006ffd72 in find_base_term(rtx_def*) ()
#75 0x00000000006ffe45 in find_base_term(rtx_def*) ()
#76 0x00000000006ffd72 in find_base_term(rtx_def*) ()
#77 0x00000000006ffe45 in find_base_term(rtx_def*) ()
#78 0x00000000006ffdb0 in find_base_term(rtx_def*) ()
#79 0x0000000000703615 in true_dependence_1(rtx_def const*,
machine_mode, rtx_def*, rtx_def const*, rtx_def*, bool) ()
#80 0x0000000000e2e771 in check_mem_read_use(rtx_def**, void*) ()
#81 0x0000000000a4122d in note_uses(rtx_def**, void (*)(rtx_def**,
void*), void*) ()
#82 0x0000000000e2f80b in rest_of_handle_dse() ()
#83 0x00000000009deb9a in execute_one_pass(opt_pass*) ()
#84 0x00000000009df3e0 in execute_pass_list_1(opt_pass*) ()
#85 0x00000000009df3f2 in execute_pass_list_1(opt_pass*) ()
#86 0x00000000009df435 in execute_pass_list(function*, opt_pass*) ()
#87 0x000000000076477d in cgraph_node::expand() ()
#88 0x0000000000765f13 in symbol_table::compile() ()
#89 0x0000000000767670 in symbol_table::finalize_compilation_unit() ()
#90 0x0000000000a994b6 in compile_file() ()

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Thomas Petazzoni]

Hello,

On Tue, 14 May 2019 09:57:00 -0500
Matthew Weber <matthew.weber@collins.com> wrote:
> > > microblazeel |                         glibmm | TIM | http://autobuild.buildroot.net/results/e196d77626b877dc3454d21febe20a04877c02a9 |  
> >
> > Another weird timeout, this time on Matt's autobuilder. Matt, could you
> > have a look ?
> >
> > But this seems to happen quite regularly, even on other autobuilder
> > machines:
> >
> >   http://autobuild.buildroot.net/?reason=glibmm
> >
> > Always on microblazeel, like the timeout on "atop" discussed above. I
> > guess that probably points at a compiler issue, which means it should
> > be reproducible.
> >  
> 
> Build definitely hung (didn't even need to be on that build machine).
> I'll hopefully get some time to take a deeper look later.

I'd say most likely it's the same Microblaze issue than on atop, which
Giulio has been looking into, and which is in fact related to
BR2_TOOLCHAIN_HAS_GCC_BUG_85180.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Giulio Benetti]

Hello,

Il 14/05/2019 17:43, Thomas Petazzoni ha scritto:
> Hello,
> 
> On Tue, 14 May 2019 09:57:00 -0500
> Matthew Weber <matthew.weber@collins.com> wrote:
>>>> microblazeel |                         glibmm | TIM | http://autobuild.buildroot.net/results/e196d77626b877dc3454d21febe20a04877c02a9 |
>>>
>>> Another weird timeout, this time on Matt's autobuilder. Matt, could you
>>> have a look ?
>>>
>>> But this seems to happen quite regularly, even on other autobuilder
>>> machines:
>>>
>>>    http://autobuild.buildroot.net/?reason=glibmm
>>>
>>> Always on microblazeel, like the timeout on "atop" discussed above. I
>>> guess that probably points at a compiler issue, which means it should
>>> be reproducible.
>>>   
>>
>> Build definitely hung (didn't even need to be on that build machine).
>> I'll hopefully get some time to take a deeper look later.
> 
> I'd say most likely it's the same Microblaze issue than on atop, which
> Giulio has been looking into, and which is in fact related to
> BR2_TOOLCHAIN_HAS_GCC_BUG_85180.

I'm going to test this too together with:
- atop(now it compiles ok)
- boost(todo)
- engine-flare(g++ seems to behave differentely from gcc, it always fail)
- glibmm(just added, todo)

Best regards
-- 
Giulio Benetti
CTO

MICRONOVA SRL
Sede: Via A. Niedda 3 - 35010 Vigonza (PD)
Tel. 049/8931563 - Fax 049/8931346
Cod.Fiscale - P.IVA 02663420285
Capitale Sociale ? 26.000 i.v.
Iscritta al Reg. Imprese di Padova N. 02663420285
Numero R.E.A. 258642

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Giulio Benetti]

Il 14/05/2019 19:12, Giulio Benetti ha scritto:
> Hello,
> 
> Il 14/05/2019 17:43, Thomas Petazzoni ha scritto:
>> Hello,
>>
>> On Tue, 14 May 2019 09:57:00 -0500
>> Matthew Weber <matthew.weber@collins.com> wrote:
>>>>> microblazeel |                         glibmm | TIM | http://autobuild.buildroot.net/results/e196d77626b877dc3454d21febe20a04877c02a9 |
>>>>
>>>> Another weird timeout, this time on Matt's autobuilder. Matt, could you
>>>> have a look ?
>>>>
>>>> But this seems to happen quite regularly, even on other autobuilder
>>>> machines:
>>>>
>>>>     http://autobuild.buildroot.net/?reason=glibmm
>>>>
>>>> Always on microblazeel, like the timeout on "atop" discussed above. I
>>>> guess that probably points at a compiler issue, which means it should
>>>> be reproducible.
>>>>    
>>>
>>> Build definitely hung (didn't even need to be on that build machine).
>>> I'll hopefully get some time to take a deeper look later.
>>
>> I'd say most likely it's the same Microblaze issue than on atop, which
>> Giulio has been looking into, and which is in fact related to
>> BR2_TOOLCHAIN_HAS_GCC_BUG_85180.
> 
> I'm going to test this too together with:
> - atop(now it compiles ok)
> - boost(todo)
> - engine-flare(g++ seems to behave differentely from gcc, it always fail)
> - glibmm(just added, todo)

- gst-ffmpeg(todo)

> 
> Best regards
> 

-- 
Giulio Benetti
CTO

MICRONOVA SRL
Sede: Via A. Niedda 3 - 35010 Vigonza (PD)
Tel. 049/8931563 - Fax 049/8931346
Cod.Fiscale - P.IVA 02663420285
Capitale Sociale ? 26.000 i.v.
Iscritta al Reg. Imprese di Padova N. 02663420285
Numero R.E.A. 258642

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Adrian Perez de Castro]

Hello,

On Mon, 13 May 2019 13:55:20 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
 
> >          arm |           wpebackend-fdo-1.0.1 | NOK | http://autobuild.buildroot.net/results/07dded285364ca342c3270ba71bdc8ef72e1db26 |     
> 
> Should be fixed by http://patchwork.ozlabs.org/patch/1085508/, but we
> still haven't received feedback from Adrian on this one.

As a matter of fact, I had already replied [1] with a ?Reviewed-by? for this
one, and I think we should merge it.

Best regards,
?Adri?n

---
[1] http://patchwork.ozlabs.org/patch/1085508/#2162729
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190515/501e943f/attachment.asc>

[Buildroot] [autobuild.buildroot.net] Build results for 2019-05-12

[Thomas Petazzoni]

Hello Adrian,

On Wed, 15 May 2019 00:13:41 +0300
Adrian Perez de Castro <aperez@igalia.com> wrote:

> Hello,
> 
> On Mon, 13 May 2019 13:55:20 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
>  
> > >          arm |           wpebackend-fdo-1.0.1 | NOK | http://autobuild.buildroot.net/results/07dded285364ca342c3270ba71bdc8ef72e1db26 |       
> > 
> > Should be fixed by http://patchwork.ozlabs.org/patch/1085508/, but we
> > still haven't received feedback from Adrian on this one.  
> 
> As a matter of fact, I had already replied [1] with a ?Reviewed-by? for this
> one, and I think we should merge it.

Sorry, I had missed this. Peter has now merged the patch, so we're all good.

Thanks a lot for your support!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com