Buildbot failure in Wildebeest Builder on whole buildset

Mark Wielaard mark@klomp.org
Wed Aug 4 20:25:59 GMT 2021


Hi,

On Wed, Aug 04, 2021 at 03:15:00PM +0000, buildbot@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/270
> 
> Buildbot URL: https://builder.wildebeest.org/buildbot/
> 
> Worker for this Build: debian-arm64
> 
> Build Reason: <unknown>
> Blamelist: CohenArthur <arthur.cohen@epita.fr>
> 
> BUILD FAILED: failed compile (failure)

This commit (and the following 3) were really bad. They didn't build.
Apparently bors doesn't check commit individually, but the buildbot
does build every commit separately.

The tree is buildable again, but I think it would be good to not have
any commits that break the build.

Periodically broken trees make it also hard to bisect issues.

Is it possible to make bors check all commits in a series? Or can we
somehow connect the buildbot workers to the bors checks?

Thanks,

Mark



More information about the Gcc-rust mailing list