Hi Arthur,
On Mon, 2022-03-07 at 15:32 +0100, Arthur Cohen wrote:
> I suspect this might be due to bors, our merging bot on github, and me
> asking it to merge multiple pull requests this morning (around 4 or 5).
> Not really sure.
>
> But the bug is fixed and properly placed in the history :)
On 3/7/22 15:23, Mark Wielaard wrote:
Hi,
On Mon, 2022-03-07 at 10:57 +0100, Arthur Cohen wrote:
This is due to the lexer's fix not being in yet. I think it should
be
resolved later as soon as bors merges the fix, but I'll check just in
case.
According to:
https://builder.wildebeest.org/build
Hi,
On Mon, 2022-03-07 at 10:57 +0100, Arthur Cohen wrote:
> This is due to the lexer's fix not being in yet. I think it should
> be
> resolved later as soon as bors merges the fix, but I'll check just in
> case.
According to:
https://builder.wildebeest.org/buildbot/#/builders?tags=gccrust
It w
Hi,
This is due to the lexer's fix not being in yet. I think it should be
resolved later as soon as bors merges the fix, but I'll check just in case.
Sorry for the noise,
Kindly,
Arthur
On 3/7/22 10:49, build...@builder.wildebeest.org wrote:
The Buildbot has detected a new failure on build
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/1720
Buildbot URL: https://builder.wildebeest.org/buildbot/
Worker for this Build: debian-arm64
Build Re
Hi Mark,
On 3/6/22 23:33, Mark Wielaard wrote:
Hi,
On Sun, Mar 06, 2022 at 11:20:56PM +0100, Mark Wielaard wrote:
On Sun, Mar 06, 2022 at 10:01:10PM +, build...@builder.wildebeest.org wrote:
The Buildbot has detected a new failure on builder gccrust-debian-arm64 while
building gccrust.
F
