public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Christophe Lyon <>
Cc: Jeff Law <>,,
Subject: Activate gcc builder problem emails (Was: [PATCH v2] genmultilib: Add sanity check)
Date: Tue, 22 Nov 2022 00:01:16 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

Hi Christophe,

On Mon, Nov 21, 2022 at 01:35:34PM +0100, Christophe Lyon wrote:
> On 11/21/22 13:32, Mark Wielaard wrote:
> > > I've just sent a fix:
> > >
> > > 
> > > Hopefully that one is right
> > 
> > The buildbot gcc builds are turning green again!
> >
> Good! I didn't imagine the feedback would be so fast :-)
> BTW, I don't remember receiving an email from the buildbot after the
> breakage, does it send such emails for binutils/gdb only?

You are right, we didn't seem to have any problem report emails for
the gcc builds. The attached (pushed) patch activates email reports
for the quick gcc builders. Whenever they fail the patch author should
get an email now. Also it will now sent email to gcc-testresults if a
build starts failing or becomes successful again.

Note that we don't have good reporting for the full gcc builders
yet. We don't have regression detection yet, so we can only see that
the full testsuite passes or fails. All results are put into the
bunsen database though.



[-- Attachment #2: 0001-Add-mail-notifiers-for-gcc-builds.patch --]
[-- Type: text/x-diff, Size: 2355 bytes --]

From adbdb81530f97880facb942afe14781c1006e283 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <>
Date: Mon, 21 Nov 2022 23:47:53 +0100
Subject: [PATCH] Add mail notifiers for gcc builds

Change gcc_fedrawhide_x86_64_builder tag from "gcc" to "gcc-full"
like other "full" builders (debian-amd64, ubuntu-armhf and ubuntu-arm64).

Add mail notifiers for builders tagged "gcc". One to sent email to
patch author if a new problem (failed build) appears. Another to
sent email to gcc-testresults whenever a build changes from success
to failed or the other way around.
 builder/master.cfg | 23 ++++++++++++++++++++++-
 1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/builder/master.cfg b/builder/master.cfg
index 61bf4f1..b25731d 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -2888,7 +2888,7 @@ gcc_fedrawhide_x86_64_builder = util.BuilderConfig(
-        tags=["gcc", "fedora", "x86_64"],
+        tags=["gcc-full", "fedora", "x86_64"],
@@ -3857,6 +3857,27 @@ mn_elfutils_try = reporters.MailNotifier(
+# Problem report for the whole gcc tagged builder set
+# Goes to patch author if a new problem appears
+generator_gcc = reporters.BuildSetStatusGenerator(
+        mode=('problem',), tags=['gcc'])
+mn_gcc = reporters.MailNotifier(
+        fromaddr="",
+        sendToInterestedUsers=True,
+        generators=[generator_gcc])
+# Change report for the whole gcc tagged builder set
+# Goes to the mailinglist if a builder result changes
+generator_gcc_change = reporters.BuildSetStatusGenerator(
+        mode=('change',), tags=['gcc'])
+mn_gcc_change = reporters.MailNotifier(
+        fromaddr="",
+        sendToInterestedUsers=False,
+        extraRecipients=[''],
+        generators=[generator_gcc_change])
 # Problem report for the whole gccrust tagged builder set
 generator_gccrust = reporters.BuildSetStatusGenerator(
         mode=('problem',), tags=['gccrust'])

           reply	other threads:[~2022-11-21 23:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).