public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
* Fwd: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
       [not found] <20230129193123.51BDE3858D35@sourceware.org>
@ 2023-01-29 19:36 ` Jerry D
  2023-01-29 19:43   ` NightStrike
  2023-01-29 19:49   ` Sam James
  0 siblings, 2 replies; 12+ messages in thread
From: Jerry D @ 2023-01-29 19:36 UTC (permalink / raw)
  To: gfortran, GCC Mailing List

I had this show up today. I have no idea what this is about.

Please advise.

Jerry


-------- Forwarded Message --------
Subject: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Sun, 29 Jan 2023 19:31:23 +0000
From: builder@sourceware.org
To: Jerry DeLisle <jvdelisle@gcc.gnu.org>

A new failure has been detected on builder gcc-gentoo-sparc while 
building gcc.

Full details are available at:
     https://builder.sourceware.org/buildbot/#builders/231/builds/210

Build state: failed configure (failure)
Revision: 8011fbba7baa46947341ca8069b5a327163a68d5
Worker: gentoo-sparc-big
Build Reason: (unknown)
Blamelist: Jerry DeLisle <jvdelisle@gcc.gnu.org>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
     Logs:
         - stdio: 
https://builder.sourceware.org/buildbot/#builders/231/builds/210/steps/1/logs/stdio

- 2: rm -rf gcc-build ( success )
     Logs:
         - stdio: 
https://builder.sourceware.org/buildbot/#builders/231/builds/210/steps/2/logs/stdio

- 3: configure ( failure )
     Logs:
         - stdio: 
https://builder.sourceware.org/buildbot/#builders/231/builds/210/steps/3/logs/stdio


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-29 19:36 ` Fwd: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master) Jerry D
@ 2023-01-29 19:43   ` NightStrike
  2023-01-29 19:49   ` Sam James
  1 sibling, 0 replies; 12+ messages in thread
From: NightStrike @ 2023-01-29 19:43 UTC (permalink / raw)
  To: Jerry D; +Cc: gfortran, GCC Mailing List

On Sun, Jan 29, 2023 at 2:37 PM Jerry D via Fortran <fortran@gcc.gnu.org> wrote:
>
> I had this show up today. I have no idea what this is about.
>
> Please advise.

I assume the buildbot thinks that
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8011fbba7baa46947341ca8069b5a327163a68d5
broke the build, but I fail to see how that commit results in the
error reported in the log.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-29 19:36 ` Fwd: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master) Jerry D
  2023-01-29 19:43   ` NightStrike
@ 2023-01-29 19:49   ` Sam James
  2023-01-30  6:27     ` Steve Kargl
  1 sibling, 1 reply; 12+ messages in thread
From: Sam James @ 2023-01-29 19:49 UTC (permalink / raw)
  To: Jerry D; +Cc: gfortran, GCC Mailing List

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



> On 29 Jan 2023, at 19:36, Jerry D via Gcc <gcc@gcc.gnu.org> wrote:
> 
> I had this show up today. I have no idea what this is about.
> 
> Please advise.
> 

Sorry Jerry, false positive -- something went wrong with the builder. Disregard.

We're still setting things up there.


> Jerry

Best,
sam

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-29 19:49   ` Sam James
@ 2023-01-30  6:27     ` Steve Kargl
  2023-01-30 13:52       ` Mark Wielaard
  0 siblings, 1 reply; 12+ messages in thread
From: Steve Kargl @ 2023-01-30  6:27 UTC (permalink / raw)
  To: Sam James via Fortran; +Cc: Jerry D, GCC Mailing List

On Sun, Jan 29, 2023 at 07:49:35PM +0000, Sam James via Fortran wrote:
> 
> 
> > On 29 Jan 2023, at 19:36, Jerry D via Gcc <gcc@gcc.gnu.org> wrote:
> > 
> > I had this show up today. I have no idea what this is about.
> > 
> > Please advise.
> > 
> 
> Sorry Jerry, false positive -- something went wrong with
> the builder. Disregard.
> 
> We're still setting things up there.
> 

Please remove the skull and cross bones in the subject line.

-- 
Steve

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-30  6:27     ` Steve Kargl
@ 2023-01-30 13:52       ` Mark Wielaard
  2023-01-30 14:46         ` Thomas Koenig
  0 siblings, 1 reply; 12+ messages in thread
From: Mark Wielaard @ 2023-01-30 13:52 UTC (permalink / raw)
  To: sgk, Sam James via Fortran; +Cc: Jerry D, GCC Mailing List

Hi Steve,

On Sun, 2023-01-29 at 22:27 -0800, Steve Kargl via Gcc wrote:
> Please remove the skull and cross bones in the subject line.

That is the default "hazard symbol" buildbot uses if a build turns from
success to failure. If you have a better suggestion you might want to
contact upstream https://buildbot.net/ We'll pick up the new default
when we'll upgrade.

Or if you think we should use a custom email template:
https://docs.buildbot.net/latest/manual/configuration/report_generators/formatter.html
You can provide a patch to buildbot@sourceware.org.
The code for our instance can be found here:
https://sourceware.org/git/builder.git

Cheers,

Mark

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-30 13:52       ` Mark Wielaard
@ 2023-01-30 14:46         ` Thomas Koenig
  2023-01-30 15:10           ` Steve Kargl
  0 siblings, 1 reply; 12+ messages in thread
From: Thomas Koenig @ 2023-01-30 14:46 UTC (permalink / raw)
  To: Mark Wielaard, sgk, Sam James via Fortran; +Cc: Jerry D, GCC Mailing List

On 30.01.23 14:52, Mark Wielaard wrote:
> Hi Steve,
> 
> On Sun, 2023-01-29 at 22:27 -0800, Steve Kargl via Gcc wrote:
>> Please remove the skull and cross bones in the subject line.
> 
> That is the default "hazard symbol" buildbot uses if a build turns from
> success to failure. If you have a better suggestion you might want to
> contact upstream https://buildbot.net/ We'll pick up the new default
> when we'll upgrade.
> 
> Or if you think we should use a custom email template:
> https://docs.buildbot.net/latest/manual/configuration/report_generators/formatter.html
> You can provide a patch to buildbot@sourceware.org.
> The code for our instance can be found here:
> https://sourceware.org/git/builder.git

I usually put e-mails with such unicode characters into my spam folder
automatically.

If that's what you want, that is fine with me.

Regards

	Thomas


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-30 14:46         ` Thomas Koenig
@ 2023-01-30 15:10           ` Steve Kargl
  2023-01-30 22:07             ` Gerald Pfeifer
  0 siblings, 1 reply; 12+ messages in thread
From: Steve Kargl @ 2023-01-30 15:10 UTC (permalink / raw)
  To: Thomas Koenig
  Cc: Mark Wielaard, Sam James via Fortran, Jerry D, GCC Mailing List

On Mon, Jan 30, 2023 at 03:46:30PM +0100, Thomas Koenig wrote:
> On 30.01.23 14:52, Mark Wielaard wrote:
> > Hi Steve,
> > 
> > On Sun, 2023-01-29 at 22:27 -0800, Steve Kargl via Gcc wrote:
> > > Please remove the skull and cross bones in the subject line.
> > 
> > That is the default "hazard symbol" buildbot uses if a build turns from
> > success to failure. If you have a better suggestion you might want to
> > contact upstream https://buildbot.net/ We'll pick up the new default
> > when we'll upgrade.
> > 
> > Or if you think we should use a custom email template:
> > https://docs.buildbot.net/latest/manual/configuration/report_generators/formatter.html
> > You can provide a patch to buildbot@sourceware.org.
> > The code for our instance can be found here:
> > https://sourceware.org/git/builder.git
> 
> I usually put e-mails with such unicode characters into my spam folder
> automatically.
> 
> If that's what you want, that is fine with me.
> 

Bingo.  In the case of non-[a-zA-Z] characters in the
Subject (or Fromi or To) line, the spam folder is normally
named /dev/null.

-- 
Steve

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-30 15:10           ` Steve Kargl
@ 2023-01-30 22:07             ` Gerald Pfeifer
  2023-01-30 22:50               ` Steve Kargl
  0 siblings, 1 reply; 12+ messages in thread
From: Gerald Pfeifer @ 2023-01-30 22:07 UTC (permalink / raw)
  To: Steve Kargl
  Cc: Thomas Koenig, Mark Wielaard, Sam James via Fortran, Jerry D, gcc

On Mon, 30 Jan 2023, Steve Kargl via Gcc wrote:
> Bingo.  In the case of non-[a-zA-Z] characters in the
> Subject (or Fromi or To) line, the spam folder is normally
> named /dev/null.

Hmm, so any digit, parenthesis, or bracket in the Subject, and mails gets 
to /dev/null?

Or having an umlaut or other special character in one's name - which is
pretty common in parts of the world like Central Europe?


"Be conservative in what you send, be liberal in what you accept."
[Postel's Law]

Gerald

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-30 22:07             ` Gerald Pfeifer
@ 2023-01-30 22:50               ` Steve Kargl
  2023-01-31 13:13                 ` Thomas Schwinge
  0 siblings, 1 reply; 12+ messages in thread
From: Steve Kargl @ 2023-01-30 22:50 UTC (permalink / raw)
  To: Gerald Pfeifer
  Cc: Thomas Koenig, Mark Wielaard, Sam James via Fortran, Jerry D, gcc

On Mon, Jan 30, 2023 at 11:07:46PM +0100, Gerald Pfeifer wrote:
> On Mon, 30 Jan 2023, Steve Kargl via Gcc wrote:
> > Bingo.  In the case of non-[a-zA-Z] characters in the
> > Subject (or Fromi or To) line, the spam folder is normally
> > named /dev/null.
> 
> Hmm, so any digit, parenthesis, or bracket in the Subject, and mails gets 
> to /dev/null?

I suppose I should have just noted characters should be members
of the Processor Character Set (18-007r1.pdf, Sec. 6.1), but I 
suspect some here have no idea what that means. 

> Or having an umlaut or other special character in one's name - which is
> pretty common in parts of the world like Central Europe?

umlaut and other special chars can trigger spam filters.
Whitelisting is used for those that matter.

Does the skull and crossbones convey anymore info than the rest of
the subject line 

    Buildbot (Sourceware): gcc - failed configure (failure) (master)  

-- 
Steve

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-30 22:50               ` Steve Kargl
@ 2023-01-31 13:13                 ` Thomas Schwinge
  2023-01-31 14:38                   ` LIU Hao
  0 siblings, 1 reply; 12+ messages in thread
From: Thomas Schwinge @ 2023-01-31 13:13 UTC (permalink / raw)
  To: sgk
  Cc: Gerald Pfeifer, Thomas Koenig, Mark Wielaard, Sam James, fortran,
	Jerry D, gcc, buildbot

Hi!

On 2023-01-30T14:50:08-0800, Steve Kargl via Fortran <fortran@gcc.gnu.org> wrote:
> Does the skull and crossbones convey anymore info than the rest of
> the subject line
>
>     Buildbot (Sourceware): gcc - failed configure (failure) (master)

They convey as much additional information as does (automated) colorful
syntax highlighting, or (manual) source code line indentation: "none" to
some, "a lot" to others.


Grüße
 Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-31 13:13                 ` Thomas Schwinge
@ 2023-01-31 14:38                   ` LIU Hao
  2023-01-31 20:18                     ` Steve Kargl
  0 siblings, 1 reply; 12+ messages in thread
From: LIU Hao @ 2023-01-31 14:38 UTC (permalink / raw)
  To: Thomas Schwinge, sgk
  Cc: Gerald Pfeifer, Thomas Koenig, Mark Wielaard, Sam James, fortran,
	Jerry D, gcc, buildbot


[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]

在 2023-01-31 21:13, Thomas Schwinge 写道:
> Hi!
> 
> On 2023-01-30T14:50:08-0800, Steve Kargl via Fortran <fortran@gcc.gnu.org> wrote:
>> Does the skull and crossbones convey anymore info than the rest of
>> the subject line
>>
>>      Buildbot (Sourceware): gcc - failed configure (failure) (master)
> 
> They convey as much additional information as does (automated) colorful
> syntax highlighting, or (manual) source code line indentation: "none" to
> some, "a lot" to others.
> 
> 

First, I'd argue that 'emoji characters imply spammer' makes little sense. Everyone can examine the 
source of all messages in this thread and their `X-Spam-Status` headers. The fact is that, so far no 
message had been given a tag for having emoji/bad/obfuscated characters in its subject.

Second, I also agree that the skull carries NO additional information. What happened? Where did it 
happen? How severe was it? What should we do about it? A skull is neither descriptive nor 
informative, and is very unfriendly for message filters. A tag there might look much more helpful, 
such as [BUILDBOT] or [FAIL].




-- 
Best regards,
LIU Hao


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
  2023-01-31 14:38                   ` LIU Hao
@ 2023-01-31 20:18                     ` Steve Kargl
  0 siblings, 0 replies; 12+ messages in thread
From: Steve Kargl @ 2023-01-31 20:18 UTC (permalink / raw)
  To: LIU Hao
  Cc: Thomas Schwinge, Gerald Pfeifer, Thomas Koenig, Mark Wielaard,
	Sam James, fortran, Jerry D, gcc, buildbot

On Tue, Jan 31, 2023 at 10:38:02PM +0800, LIU Hao wrote:
> 在 2023-01-31 21:13, Thomas Schwinge 写道:
> > Hi!
> > 
> > On 2023-01-30T14:50:08-0800, Steve Kargl via Fortran <fortran@gcc.gnu.org> wrote:
> > > Does the skull and crossbones convey anymore info than the rest of
> > > the subject line
> > > 
> > >      Buildbot (Sourceware): gcc - failed configure (failure) (master)
> > 
> > They convey as much additional information as does (automated) colorful
> > syntax highlighting, or (manual) source code line indentation: "none" to
> > some, "a lot" to others.
> > 
> > 
> 
> First, I'd argue that 'emoji characters imply spammer' makes little sense.
> Everyone can examine the source of all messages in this thread and their
> `X-Spam-Status` headers. The fact is that, so far no message had been given
> a tag for having emoji/bad/obfuscated characters in its subject.
> 

The irony! Your email ended up in one of my spam folders.

X-junkfilter: 20020519
X-Spammer: bodychk-domains: 126.com>
        domains: 126.com

-- 
Steve

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2023-01-31 20:18 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20230129193123.51BDE3858D35@sourceware.org>
2023-01-29 19:36 ` Fwd: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master) Jerry D
2023-01-29 19:43   ` NightStrike
2023-01-29 19:49   ` Sam James
2023-01-30  6:27     ` Steve Kargl
2023-01-30 13:52       ` Mark Wielaard
2023-01-30 14:46         ` Thomas Koenig
2023-01-30 15:10           ` Steve Kargl
2023-01-30 22:07             ` Gerald Pfeifer
2023-01-30 22:50               ` Steve Kargl
2023-01-31 13:13                 ` Thomas Schwinge
2023-01-31 14:38                   ` LIU Hao
2023-01-31 20:18                     ` Steve Kargl

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).