Buildbot failure in Wildebeest Builder on whole buildset
The Buildbot has detected a new failure on builder gccrust-debian-arm64 while building gccrust. Full details are available at: https://builder.wildebeest.org/buildbot/#builders/58/builds/1609 Buildbot URL: https://builder.wildebeest.org/buildbot/ Worker for this Build: debian-arm64 Build Reason: Blamelist: Philip Herron BUILD FAILED: failed compile (failure) Sincerely, -The Buildbot -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Buildbot failure in Wildebeest Builder on whole buildset
Hi, On Tue, Jan 25, 2022 at 11:42:41PM +0100, Mark Wielaard wrote: > 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. This seems to work as expected and has the additional benefit of skipping those "merge" commits by bors since those don't actually change any files. Under https://builder.wildebeest.org/buildbot/#/changes you can see the "builds" for each change (some will now be empty if they didn't touch any gccrs files). Cheers, Mark -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Buildbot failure in Wildebeest Builder on whole buildset
Hi, On Sat, Jan 29, 2022 at 04:20:57PM +, build...@builder.wildebeest.org wrote: > The Buildbot has detected a new failure on builder gccrust-debian-arm64 while > building gccrust. > Full details are available at: > https://builder.wildebeest.org/buildbot/#builders/58/builds/1609 > > Buildbot URL: https://builder.wildebeest.org/buildbot/ > > Worker for this Build: debian-arm64 > > Build Reason: > Blamelist: Philip Herron > > BUILD FAILED: failed compile (failure) That is somewhat odd. It was the oom-killer: oom_reaper: reaped process 25752 (ld), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB But the next builds succeeded. I am not sure what caused the out of memory this time. Cheers, Mark -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
