Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
On 1/30/23 5:46 AM, Sam James wrote: On 30 Jan 2023, at 06:27, Steve Kargl via Gcc wrote: Hi Steve, Please remove the skull and cross bones in the subject line. This is a sourceware project so I've CC'd the buildbot mailing list where we discuss these matters. Does the emoji bother you, or is it the skull and crossbones specifically (which is a recognised symbol for a hazard)? Note that this is the default upstream from the Buildbot project (we use their software) too. We haven't chosen it ourselves. Thanks, sam As long as your asking it just looks stupid, childish to think anyone needs an emoji in what we try think is a professional product. ( Too informal? ) If that's not enough, how about corny, or something for 12 year olds. Yep, it's just stupid. I don't have an issue with bots, I just don't need emojis outside of my personal chats on my phone. If it is suppose to be a notification, how about just the word "Alert" or "Notice" Regards, Jerry Jerry
Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
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
Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
On 30.01.23 23:07, Gerald Pfeifer wrote: Hmm, so any digit, parenthesis, or bracket in the Subject, and mails gets to /dev/null? Sending mail with special graphics in Subject lines is what spammers do, to attract special attention. (And no, umlauts are not included :-). So, If I ever happen to break bootstrap, I will not learn about it from a mail that uses spammer's techniques. A regular mail, on the other hand, I would read. Regards Thomas
Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
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
Sourceware network outage, Tuesday 2023-01-31
We've received word from our data centre hosts that they will have a network infrastructure outage tomorrow, Tuesday 2023-01-31, between 8am and 12am EST (UTC-5). We may follow that up with a server firmware-related update/boot. This impacts sourceware.org, builder.sourceware.org, patchwork.sourceware.org, inbox.sourceware.org, valgrind.org, elfutils.org, cygwin.com and gcc.gnu.org, which all may be unreachable for a couple of hours. Note that there are read-only mirrors of the git repositories at https://sr.ht/~sourceware/ if you need access during the outage. Please feel free to hang out at irc.libera.chat #overseers to follow the current status.
Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
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 build...@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
Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
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 build...@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
Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
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 build...@sourceware.org. The code for our instance can be found here: https://sourceware.org/git/builder.git Cheers, Mark
Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
> On 30 Jan 2023, at 06:27, Steve Kargl via Gcc wrote: Hi Steve, > Please remove the skull and cross bones in the subject line. This is a sourceware project so I've CC'd the buildbot mailing list where we discuss these matters. Does the emoji bother you, or is it the skull and crossbones specifically (which is a recognised symbol for a hazard)? Note that this is the default upstream from the Buildbot project (we use their software) too. We haven't chosen it ourselves. Thanks, sam signature.asc Description: Message signed with OpenPGP
