"Jiang, Haochen" writes:
> Ping for this thread.
>
> Any ideas? If no, I will change the generated info with command following
> if we take r15-1643 as example and see if it is clearer:
>
> head -26 makelog.r15-1643.x86_64.native | tail -7 > 1.log;
> grep -E "(error:|Error)" makelog.r15-1643.x86_64.native >> 1.log;
> echo " Detailed Info around error (+- 10 Lines)
> " >> 1.log;
> grep -C 10 -E "error:" makelog.r15-1643.x86_64.native >> 1.log;
>
This plan sounds good to me, although I was hoping someone might speak
up ;)
I will keep an eye on the failures afterwards and then see if it looks
OK too.
(Sorry if you were waiting on me, I may have misunderstood.)
> Thx,
> Haochen
>
>> -Original Message-
>> From: Jiang, Haochen
>> Sent: Thursday, July 18, 2024 3:57 PM
>> To: 'Sam James'
>> Cc: 'gcc-regression@gcc.gnu.org' ; 'gcc-
>> testresu...@gcc.gnu.org' ; 'g...@gcc.gnu.org'
>>
>> Subject: RE: gcc-regression script build fail info
>>
>>
>>
>> > -Original Message-
>> > From: Jiang, Haochen
>> > Sent: Thursday, July 18, 2024 3:46 PM
>> > To: 'Sam James'
>> > Cc: 'gcc-regression@gcc.gnu.org' ; 'gcc-
>> > testresu...@gcc.gnu.org' ; g...@gcc.gnu.org
>> > Subject: gcc-regression script build fail info
>> >
>> > > > For future reports, would it be possible to change the grep to
>> > > > something
>> > > > like:
>> > > >
>> > > > grep -E "(error:|Error)" or just grep -rsin "error" -w or something.
>> > > >
>> > > > This would allow catching the actual compile error in libbacktrace
>> > > > if it's not going to fit in the last N lines from make.
>> > >
>> > > Hi Sam,
>> > >
>> > > Let me change that in the script and see if it is much clearer.
>> > >
>> > > This bug report definitely seems not clear for me also.
>> >
>> > Hi all,
>> >
>> > Sam just mentioned in another thread that the current log for build fail in
>> gcc-
>> > regression is not clear at all, like the problem in:
>> > https://gcc.gnu.org/pipermail/gcc-regression/2024-July/080272.html
>> > The 100 bottom line didn't give any info for why it runs into a build fail.
>> >
>> > As Sam suggested, we might change the build fail info part which is
>> > currently
>> > using 'tail -100' to 'grep -E "(error:|Error)"' to get some clear info.
>> >
>> > Does any one still needs the 'tail -100' for some more info? Or if the
>> > output
>> for
>> > 'grep -E "(error:|Error)" is enough?
>> >
>> > For example, for r15-2116, overall report will be:
>>
>> Made a typo here, the report is generated from r15-1643.
>>
>> >
>> > make[2]: Entering directory '/home/haochenj/src/gcc-regression'
>> > rm -rf bld
>> > mkdir -p bld
>> > cd bld; \
>> > RUNTESTFLAGS="--target_board='unix{-m32,}'" ../src-master/configure \
>> > --with-arch=native --with-cpu=native --enable-clocale=gnu --with-
>> system-
>> > zlib --enable-shared --enable-cet --with-demangler-in-ld --enable-libmpx --
>> > prefix=/usr/gcc-15.0.0 --with-fpmath=sse checking build system type...
>> > x86_64-pc-linux-gnu
>> > grep "Error " makelog.r15-1643.x86_64.native >> makelog.r15-
>> > 1643.x86_64.native.mail; \
>> > make[6]: [Makefile:1832: x86_64-pc-linux-gnu/bits/largefile-config.h] Error
>> 1
>> > (ignored)
>> > make[6]: [Makefile:1831: x86_64-pc-linux-gnu/bits/largefile-config.h] Error
>> 1
>> > (ignored)
>> > make[6]: [Makefile:1832: x86_64-pc-linux-gnu/bits/largefile-config.h] Error
>> 1
>> > (ignored)
>> > ../../src-master/gcc/config/i386/i386.cc:107:12: error: 'rtx_def*
>> > legitimize_dllimport_symbol(rtx, bool)' declared 'static' but never
>> > defined [-
>> > Werror=unused-function]
>> > ../../src-master/gcc/config/i386/i386.cc:108:12: error: 'rtx_def*
>> > legitimize_pe_coff_extern_decl(rtx, bool)' declared 'static' but never
>> > defined
>> [-
>> > Werror=unused-function]
>> > make[6]: *** [Makefile:2557: i386.o] Error 1
>> > make[5]: *** [Makefile:5108: all-stage2-gcc] Error 2
>> > make[4]: *** [Makefile:30031: stage2-bubble] Error 2
>> > make[3]: *** [Makefile:30275: bootstrap] Error 2
>> > make[2]: *** [Makefile:313: bootstrap] Error 2
>> > make[1]: *** [Makefile:409: one] Error 1
>> > make: *** [Makefile:406: one-master] Error 2
>> >
>> > Thx,
>> > Haochen
>> >
>> > >
>> > > Thx,
>> > > Haochen
>> > >
>> > > >
>> > > > (Not needed here as ILT already fixed the issue on master).
>> > > >
>> > > > thanks,
>> > > > sam
signature.asc
Description: PGP signature
