Re: buildbot vs --enable-targets=all

Hi Alan,

On Tue, 2022-07-26 at 21:16 +0930, Alan Modra wrote:
> On Tue, Jul 26, 2022 at 10:54:12AM +0930, Alan Modra wrote:
> > On Mon, Jul 25, 2022 at 02:25:42PM +0200, Mark Wielaard wrote:
> > > On debian-ppc64 and fedora-ppc64le there are the following ld
> > > failures:
> > > https://builder.sourceware.org/buildbot/#builders/86/builds/343
> > > https://builder.sourceware.org/buildbot/#builders/78/builds/382
> > > 
> > > extra lines in dump.out starting with "^    40: 0000002c     0
> > > TLS     GLOBAL DEFAULT    9 ie0$"
> > > EOF from /var/lib/buildbot/workers/wildebeest/binutils-debian-
> > > ppc64/binutils-gdb/ld/testsuite/ld-powerpc/tlsexe32.r
> > > FAIL: TLS32 dynamic exec
> > [...]
> Oh, you tricked me.  It's not just a single "extra line in.." but a
> bunch of differences then finally that one.

Apologies, I didn't mean to deceive. Just copy/pasted not enough
context.

The full logs files can be found in the bunsendb (see the upload bunsen
step):
https://builder.sourceware.org/testrun/b2ea62b46f245693bf32bdfdabedf95cdc31bd4f

The webwidget has a dejagnu parse view:
https://builder.sourceware.org/testrun/b2ea62b46f245693bf32bdfdabedf95cdc31bd4f?focus=dgsummary

Which you can then use to get at the specific part of the .log file for
an .exp per test:
https://builder.sourceware.org/testrun/b2ea62b46f245693bf32bdfdabedf95cdc31bd4f?dgexpfile=ld-powerpc%2Fpowerpc.exp

In this case:
https://builder.sourceware.org/testrun/b2ea62b46f245693bf32bdfdabedf95cdc31bd4f?filename=ld%2Fld.log&fileline=53358&linewindow=20#line53358

> So for some reason there is an empty .data section, putting all the
> rest of the dump off by one.
> 
> regexp_diff match failure
> regexp "^ +\[[ 0-9]+\] \.symtab +SYMTAB +.*$"
> line   "  [13] .data             PROGBITS        01810398 000398
> 000000 00  WA  0   0  1"
> regexp_diff match failure
> regexp "^ +\[[ 0-9]+\] \.strtab +STRTAB +.*$"
> line   "  [14] .symtab           SYMTAB          00000000 000398
> 000290 10     15  26  4"
> regexp_diff match failure

Thanks. I don't know where that is coming from. It is curious that it
happens on both debian-ppc64 and fedora-ppc64le which are somewhat
different environments.

Cheers,

Mark