Hi,
On Tue, Jan 25, 2022 at 08:33:50AM +0100, Thomas Schwinge wrote:
> On 2022-01-24T22:30:21+0100, Marc via Gcc-rust <gcc-rust@gcc.gnu.org> wrote:
> > Mark Wielaard <m...@klomp.org> writes:
> >> Sorry, I don't immediately know what is happening.
> >> I assume some merge took place and the buildbot doesn't know what are
> >> good/bad commits and just tries to do builds for everything in the
> >> merge. I have shutdown the buildbot till I have time to figure out what
> >> is going on.
> >
> > Yes, it seems Thomas did a merge in
> > 21af490baa734a901fb798bc2ac4df62109bc895, bringing gcc's master from a
> > few days back :) [490e23032baaece71f2ec09fa1805064b150fbc2]
>
> Yes, I did. Mark, should I announce that in advance from now on?
I added a filesIsImportant filter to the buildbot gccrs scheduler:
gccrs_files = ["gcc/rust/", "gcc/testsuite/rust/", "gcc/config/.*/*-rust.c"]
def gccrsImportant(change):
for file in change.files:
for pattern in gccrs_files:
match = re.match(pattern, file)
if match:
return True
return False
I think that should make sure that in the future any commits that
aren't part of the gccrs frontend won't trigger a build.
Cheers,
Mark
--
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust
