RE: ☠ Buildbot (Sourceware): gcc-autoregen - failed compile (failure) (master)

2024-11-24 Thread Jiang, Haochen via Gcc-testresults
> From: Jiang, Haochen > Sent: Monday, November 25, 2024 2:03 PM > > > From: Jiang, Haochen > > Sent: Monday, November 25, 2024 1:52 PM > > > > > From: buil...@sourceware.org > > > Sent: Monday, November 25, 2024 11:40 AM > > > > > > A new failure has been detected on builder gcc-autoregen while

RE: ☠ Buildbot (Sourceware): gcc-autoregen - failed compile (failure) (master)

2024-11-24 Thread Jiang, Haochen via Gcc-testresults
> From: Jiang, Haochen > Sent: Monday, November 25, 2024 1:52 PM > > > From: buil...@sourceware.org > > Sent: Monday, November 25, 2024 11:40 AM > > > > A new failure has been detected on builder gcc-autoregen while building gcc. > > > > Full details are available at: > > > > https://builder.sour

RE: ☠ Buildbot (Sourceware): gcc-autoregen - failed compile (failure) (master)

2024-11-24 Thread Jiang, Haochen via Gcc-testresults
> From: buil...@sourceware.org > Sent: Monday, November 25, 2024 11:40 AM > > A new failure has been detected on builder gcc-autoregen while building gcc. > > Full details are available at: > https://builder.sourceware.org/buildbot/#/builders/269/builds/10198 > > Build state: failed compile

RE: gcc-regression script build fail info

2024-08-14 Thread Jiang, Haochen via Gcc-testresults
> -Original Message- > From: Sam James > Sent: Thursday, August 15, 2024 6:30 AM > To: Jiang, Haochen > Cc: gcc-regress...@gcc.gnu.org; gcc-testresults@gcc.gnu.org; > g...@gcc.gnu.org > Subject: Re: gcc-regression script build fail info > > "Jiang, Haochen" writes: > > > Ping for this

RE: gcc-regression script build fail info

2024-08-12 Thread Jiang, Haochen via Gcc-testresults
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 "=

RE: gcc-regression script build fail info

2024-07-18 Thread Jiang, Haochen via Gcc-testresults
> -Original Message- > From: Jiang, Haochen > Sent: Thursday, July 18, 2024 3:46 PM > To: 'Sam James' > Cc: 'gcc-regress...@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 possib

gcc-regression script build fail info

2024-07-18 Thread Jiang, Haochen via Gcc-testresults
> > 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 ma

RE: master branch: commit r15-2116 failed to bootstrap on Linux/x86_64 (commit r15-2111 builds)!

2024-07-17 Thread Jiang, Haochen via Gcc-testresults
> -Original Message- > From: Sam James > Sent: Thursday, July 18, 2024 12:48 PM > To: haoch...@gnu-skx-1.sc.intel.com > Cc: gcc-regress...@gcc.gnu.org; gcc-testresults@gcc.gnu.org; Jiang, Haochen > > Subject: Re: master branch: commit r15-2116 failed to bootstrap on > Linux/x86_64 (commit