Hi,
On Sat, 2022-02-05 at 16:58 +0000, 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/1620
>
> Buildbot URL: https://builder.wildebeest.org/buildbot/
>
> Worker for this Build: debian-arm64
>
> Build Reason: <unknown>
> Blamelist: CohenArthur <arthur.co...@epita.fr>, bors[bot]
> <26634292+bors[bot]@users.noreply.github.com>
>
> BUILD FAILED: failed compile (failure)
This was caused by two commits being flipped:
commit bc47ace0ec97ef1b3498c17ff03e2ee873743d5c
Author: CohenArthur <cohenarthur....@gmail.com>
Date: Tue Jan 25 13:59:06 2022 +0100
selftest: Move C specific tests in c_family_test()
commit 2b1345a73654cf5b2b13e334813ee97016ba5d1a
Author: CohenArthur <arthur.co...@epita.fr>
Date: Tue Oct 19 10:46:45 2021 +0200
selftest: Enable unit testing for the rust frontend
So the first commit enabled the selftests (which fails in the buildbot)
and the second moved the C specific selftests (which just failed) into
c_family_tests so they won't trigger a failure next time.
Unfortunately the buildbot thinks the second commit isn't rust frontend
related (which is technically correct) and so won't do a build with
that commit.
But the next gccrs commit should turn the buildbot green again.
Cheers,
Mark
--
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust
