From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [PATCH] Add email notifiers for gcc and gdb-binutils autoregen builders
Date: Tue, 14 Nov 2023 13:33:49 +0100 [thread overview]
Message-ID: <20231114123349.340516-1-mark@klomp.org> (raw)
---
builder/master.cfg | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/builder/master.cfg b/builder/master.cfg
index b59adf2..b50cab6 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -4925,6 +4925,31 @@ mn_gcc_change = reporters.MailNotifier(
generators=[generator_gcc_change])
c['services'].append(mn_gcc_change)
+# Problem report for autotools regeneration
+# Includes logs because they are small (and include the diff)
+generator_gcc_autotools_problem = reporters.BuildStatusGenerator(
+ tags=["gcc-autotools"],
+ add_logs=True,
+ mode=('problem',))
+mn_gcc_autools_change = reporters.MailNotifier(
+ fromaddr="builder@sourceware.org",
+ sendToInterestedUsers=True,
+ extraRecipients=['gcc-testresults@gcc.gnu.org'],
+ generators=[generator_gcc_autotools_problem])
+c['services'].append(mn_gcc_autools_change)
+
+generator_binutils_gdb_autotools_problem = reporters.BuildStatusGenerator(
+ tags=["binutils-gdb-autotools"],
+ add_logs=True,
+ mode=('problem',))
+mn_binutils_gdb_autools_change = reporters.MailNotifier(
+ fromaddr="builder@sourceware.org",
+ sendToInterestedUsers=True,
+ extraRecipients=['binutils@sourceware.org',
+ 'gdb-testers@sourceware.org'],
+ generators=[generator_binutils_gdb_autotools_problem])
+c['services'].append(mn_binutils_gdb_autools_change)
+
# Problem report for the whole gccrust tagged builder set
#generator_gccrust = reporters.BuildSetStatusGenerator(
# mode=('problem',), tags=['gccrust'])
--
2.41.0
reply other threads:[~2023-11-14 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231114123349.340516-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).