Buildbot failure in Wildebeest Builder on whole buildset

[Philip Herron]

On 04/08/2021 21:25, Mark Wielaard wrote:
> 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
>
Hi Mark,

I think the build-bot checks for every commit is a really nice feature
here. I think you should keep the build-bots as are. I really like to
make sure each of my commits are build-able and pass tests. It keeps me
honest to avoid regressions as best I can.

What do you think?

Thanks

--Phil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 665 bytes
Desc: OpenPGP digital signature
URL: <https://gcc.gnu.org/pipermail/gcc-rust/attachments/20210806/bf9752e0/attachment.sig>