Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)

[Mike Frysinger <vapier@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 2902 bytes --]

On 23 Dec 2022 14:10, Indu Bhagat via Binutils wrote:
> On 12/23/22 1:30 PM, builder--- via Binutils wrote:
> > A new failure has been detected on builder binutils-debian-ppc64 while building binutils-gdb.
> > 
> > Full details are available at:
> >      https://builder.sourceware.org/buildbot/#builders/78/builds/1218
> > 
> > Build state: failed test (failure)
> > Revision: 995bc59782363e7634fe3034aa9363528cb8b2e5
> > Worker: debian-ppc64
> > Build Reason: (unknown)
> > Blamelist: Indu Bhagat <indu.bhagat@oracle.com>, Mike Frysinger <vapier@gentoo.org>, Simon Marchi <simon.marchi@polymtl.ca>
> > 
> > Steps:
> > 
> > - 0: worker_preparation ( success )
> > 
> > - 1: git checkout ( success )
> >      Logs:
> >          - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/1/logs/stdio
> > 
> > - 2: rm -rf binutils-build ( success )
> >      Logs:
> >          - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/2/logs/stdio
> > 
> > - 3: configure ( success )
> >      Logs:
> >          - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/3/logs/stdio
> > 
> > - 4: make ( warnings )
> >      Logs:
> >          - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/4/logs/stdio
> >          - warnings (22): https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/4/logs/warnings__22_
> > 
> > - 5: make check ( failure )
> >      Logs:
> >          - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/stdio
> >          - ld.sum: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/ld_sum
> >          - ld.log: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/ld_log
> >          - gas.sum: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/gas_sum
> >          - gas.log: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/gas_log
> >          - binutils.sum: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/binutils_sum
> >          - binutils.log: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/binutils_log
> >          - libsframe.sum: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/libsframe_sum
> >          - libsframe.log: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/libsframe_log
> >          - warnings (8): https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/warnings__8_
> > 
> 
> I am looking into the failure (FAIL: encode-1: Encode buffer match). 
> Basically this test should not be run as is on a big endian host.

that sounds incorrect.  tests shouldn't depend on the endian of the host.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]