From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] Set onlyImportant=True for gccrust, binutils and gdb schedulers
Date: Wed, 8 Jun 2022 22:50:27 +0200 [thread overview]
Message-ID: <20220608205027.677119-1-mark@klomp.org> (raw)
The gccrust, binutils and gdb schedulers have fileIsImportant filters.
This means a build is only done for changes in "important"
file. Setting onlyImportant=True makes sure that changesets aren't
generated for changes in files that aren't really part of the project.
This is mainly so that a change to e.g. gas will not get added as an
"unimportant" change for gdb. Otherwise when there is a regression the
author of the "unimportant" change will also get a notification.
---
builder/master.cfg | 3 +++
1 file changed, 3 insertions(+)
diff --git a/builder/master.cfg b/builder/master.cfg
index b4b42ae..6d52e02 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -404,6 +404,7 @@ gccrust_scheduler = schedulers.SingleBranchScheduler(
change_filter=util.ChangeFilter(project="gccrust",
branch="master"),
fileIsImportant=gccrsImportant,
+ onlyImportant=True,
reason="gccrust project master branch gccrs files update",
builderNames=["gccrust-fedora-x86_64",
"gccrust-debian-i386",
@@ -436,6 +437,7 @@ binutils_scheduler = schedulers.SingleBranchScheduler(
change_filter=util.ChangeFilter(project="binutils-gdb",
branch="master"),
fileIsImportant=binutilsImportant,
+ onlyImportant=True,
reason="binutils-gdb project master branch binutils files update",
builderNames=["binutils-debian-amd64",
"binutils-fedora-x86_64",
@@ -480,6 +482,7 @@ gdb_scheduler = schedulers.SingleBranchScheduler(
change_filter=util.ChangeFilter(project="binutils-gdb",
branch="master"),
fileIsImportant=gdbImportant,
+ onlyImportant=True,
reason="binutils-gdb project master branch gdb files update",
builderNames=["gdb-centos-x86_64",
"gdb-fedora-x86_64",
--
2.30.2
reply other threads:[~2022-06-08 20:50 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=20220608205027.677119-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).