Hi everyone,
Sorry for the failure! Here's the explanation of why it happened:
I created a pull request for a64a5cf77c9685aa623ec69168e7f50324a102b9:
```
commit a64a5cf77c9685aa623ec69168e7f50324a102b9
(origin/invalid-macro-match-fix, invalid-macro-match-fix)
Author: Arthur Cohen
Date: Fri
Hi,
On Tue, Mar 22, 2022 at 12:41:01PM +, 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/1770
>
> Bui
Hi Mark,
On 3/7/22 15:42, Mark Wielaard wrote:
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
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
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
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.
> > Full details are available at:
> >
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.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/58/builds/1716
>
> Buildbot
Hi Thomas, thanks a lot!
On 3/2/22 13:36, Thomas Schwinge wrote:
Hi Arthur!
On 2022-03-02T13:05:30+0100, Arthur Cohen wrote:
On 3/2/22 11:05, Thomas Schwinge wrote:
On 2022-03-02T10:44:38+0100, I wrote:
On 2022-03-02T09:03:48+, Philip Herron wrote:
Yet again the build bots are out doi
Hi Arthur!
On 2022-03-02T13:05:30+0100, Arthur Cohen wrote:
> On 3/2/22 11:05, Thomas Schwinge wrote:
>> On 2022-03-02T10:44:38+0100, I wrote:
>>> On 2022-03-02T09:03:48+, Philip Herron
>>> wrote:
Yet again the build bots are out doing github automation :D. Would you
be able to gi
Hi everyone,
On 3/2/22 11:05, Thomas Schwinge wrote:
Hi!
On 2022-03-02T10:44:38+0100, I wrote:
On 2022-03-02T09:03:48+, Philip Herron wrote:
Yet again the build bots are out doing github automation :D. Would you
be able to give Arthur access to the failing buildbot to test his fix?
I s
Hi!
On 2022-03-02T10:44:38+0100, I wrote:
> On 2022-03-02T09:03:48+, Philip Herron wrote:
>> Yet again the build bots are out doing github automation :D. Would you
>> be able to give Arthur access to the failing buildbot to test his fix?
>
> I suggest as a first step to figure out why your lo
Hi,
On Wed, 2022-03-02 at 09:03 +, Philip Herron wrote:
> Yet again the build bots are out doing github automation :D. Would
> you
> be able to give Arthur access to the failing buildbot to test his
> fix?
Sure. Arthur can you sent me your ssh pubkey?
> We think we know what the issue is. We
Hi!
On 2022-03-02T09:03:48+, Philip Herron wrote:
> Yet again the build bots are out doing github automation :D. Would you
> be able to give Arthur access to the failing buildbot to test his fix?
I suggest as a first step to figure out why your local build aren't
running into this issue. Wh
Yet again the build bots are out doing github automation :D. Would you
be able to give Arthur access to the failing buildbot to test his fix?
We think we know what the issue is. We changed the lexer so we could
give it a buffer instead of a file for macro expansion, but the string
is going out of s
Hi!
On 2022-03-02T00:15:41+0100, Mark Wielaard wrote:
> On Tue, Mar 01, 2022 at 07:08:15PM +, 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://build
Hi,
On Tue, Mar 01, 2022 at 07:08:15PM +, 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/1710
>
> Bui
Hi,
On Wed, Feb 23, 2022 at 12:26:26PM +0100, Mark Wielaard wrote:
> So there were 3 issues:
>
> - The debian-i386 build had pre-existing failures that weren't
> reported before.
> - The recent commits introduced some tests which failed, and then
> some code changes that fixed those tests so
Hi,
On Wed, 2022-02-23 at 11:35 +0100, Mark Wielaard wrote:
> So, this works as expected. Note that it reports issues not just for
> debian-i386, but also for some other arches (all debian based). The
> i386 issues are not new. But the others do seem to be caused by the
> latest commit. I haven't
Hi,
So, this works as expected. Note that it reports issues not just for
debian-i386, but also for some other arches (all debian based). The
i386 issues are not new. But the others do seem to be caused by the
latest commit. I haven't investigated why yet though.
The buildbot links also point to t
Hi Mark,
Mark Wielaard writes:
> Hi Marc, Hi Tom,
>
> On Fri, Feb 18, 2022 at 12:48:23PM +, dkm--- via Gcc-rust wrote:
>> > Worker for this Build: debian-ppc64
>>
>> Looks like the ppc64 is requesting a bigger disk :)
>>
>> fatal: sha1 file
>> '/var/lib/buildbot/workers/wildebeest/gccrust
Hi Marc, Hi Tom,
On Fri, Feb 18, 2022 at 12:48:23PM +, dkm--- via Gcc-rust wrote:
> > Worker for this Build: debian-ppc64
>
> Looks like the ppc64 is requesting a bigger disk :)
>
> fatal: sha1 file
> '/var/lib/buildbot/workers/wildebeest/gccrust-debian-ppc64/gccrs/.git/index.lock'
> write
> Worker for this Build: debian-ppc64
Hi Mark,
Looks like the ppc64 is requesting a bigger disk :)
fatal: sha1 file
'/var/lib/buildbot/workers/wildebeest/gccrust-debian-ppc64/gccrs/.git/index.lock'
write error. Out of diskspace
Cheers,
Marc
--
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
http
Hi,
On Thu, Feb 17, 2022 at 10:05:29PM +0100, Mark Wielaard wrote:
> On Thu, Feb 17, 2022 at 08:46:01PM +0100, Marc via Gcc-rust wrote:
> > ../gccrs/gcc/rust/hir -I ../../gccrs/gcc/rust/resolve -I
> > ../../gccrs/gcc/rust/util -I ../../gccrs/gcc/rust/typecheck -I
> > ../../gccrs/gcc/rust/lint
Hi Marc,
On Thu, Feb 17, 2022 at 08:46:01PM +0100, Marc via Gcc-rust wrote:
> build...@builder.wildebeest.org writes:
>
> > Build Reason:
> > Blamelist: Philip Herron
>
> g++ -fno-PIE -c -DIN_GCC_FRONTEND -g -O2 -DIN_GCC -fno-exceptions
> -fno-rtti -fasynchronous-unwind-tables -W -W
build...@builder.wildebeest.org writes:
> Build Reason:
> Blamelist: Philip Herron
g++ -fno-PIE -c -DIN_GCC_FRONTEND -g -O2 -DIN_GCC -fno-exceptions
-fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-vir
Hi,
On Sat, 2022-02-05 at 16:58 +, 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 U
Hi Thomas,
On Thu, 2022-02-03 at 21:55 +0100, Thomas Schwinge wrote:
> On 2022-01-29T21:20:45+0100, Mark Wielaard wrote:
> > 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 = ["g
Hi Mark!
On 2022-01-29T21:20:45+0100, Mark Wielaard wrote:
> 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"]
Is that last one co
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
>
> Bui
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 p
Hi,
On Tue, Jan 25, 2022 at 08:33:50AM +0100, Thomas Schwinge wrote:
> On 2022-01-24T22:30:21+0100, Marc via Gcc-rust wrote:
> > Mark Wielaard writes:
> >> Sorry, I don't immediately know what is happening.
> >> I assume some merge took place and the buildbot doesn't know what are
> >> good/bad
Hi!
On 2022-01-24T22:30:21+0100, Marc via Gcc-rust wrote:
> Mark Wielaard writes:
>
>> Sorry, I don't immediately know what is happening.
>> I assume some merge took place and the buildbot doesn't know what are
>> good/bad commits and just tries to do builds for everything in the
>> merge. I hav
Mark Wielaard writes:
> Sorry, I don't immediately know what is happening.
> I assume some merge took place and the buildbot doesn't know what are
> good/bad commits and just tries to do builds for everything in the
> merge. I have shutdown the buildbot till I have time to figure out what
> is go
Hi,
On Mon, 2022-01-24 at 12:29 +, 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/1581
>
> Buildbot U
On Sun, 2021-12-19 at 17:13 +, build...@builder.wildebeest.org
wrote:
> The Buildbot has detected a new failure on builder gccrust-debian-
> ppc64 while building gccrust.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/64/builds/6
>
> Buildbot URL: http
Hi,
On Fri, 2021-11-05 at 13:49 +, build...@builder.wildebeest.org
wrote:
> The Buildbot has detected a new failure on builder gccrust-fedora-
> s390x while building gccrust.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/63/builds/1072
>
> Buildbot U
On Sat, Sep 25, 2021 at 12:04:01PM +, 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/469
O fun. I hadn
Hi,
On Sun, Aug 22, 2021 at 03:55:47PM +, 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/355
This see
On Sun, Aug 08, 2021 at 12:51:47PM +0100, Philip Herron wrote:
> I would be interested in seeing 32bit build bots since this patch has
> been merged: https://github.com/Rust-GCC/gccrs/pull/614
>
> Which thanks to Adrian who has been testing it out.
>
> Do you have access to 32bit machines? I have
On 06/08/2021 16:55, cohenarthur.dev wrote:
> On 21/08/06 03:31PM, Philip Herron wrote:
>> On 04/08/2021 21:25, Mark Wielaard wrote:
>>> Hi,
>>>
>>> On Wed, Aug 04, 2021 at 03:15:00PM +, build...@builder.wildebeest.org
>>> wrote:
The Buildbot has detected a new failure on builder gccrust-
On 06/08/2021 23:39, Mark Wielaard wrote:
> Hi Philip,
>
> On Fri, Aug 06, 2021 at 03:31:07PM +0100, Philip Herron wrote:
>>> Is it possible to make bors check all commits in a series? Or can we
>>> somehow connect the buildbot workers to the bors checks?
>> I think the build-bot checks for every c
Hi Arthur,
On Fri, Aug 06, 2021 at 05:55:09PM +0200, cohenarthur.dev via Gcc-rust wrote:
> I'm really sorry about not having all the commits build. I tried to keep
> them as atomic as possible and clearly didn't check all of them
> separately. This could have been a single commit and would have av
Hi Philip,
On Fri, Aug 06, 2021 at 03:31:07PM +0100, Philip Herron wrote:
> > Is it possible to make bors check all commits in a series? Or can we
> > somehow connect the buildbot workers to the bors checks?
>
> I think the build-bot checks for every commit is a really nice feature
> here. I thin
On 21/08/06 03:31PM, Philip Herron wrote:
> On 04/08/2021 21:25, Mark Wielaard wrote:
> > Hi,
> >
> > On Wed, Aug 04, 2021 at 03:15:00PM +, build...@builder.wildebeest.org
> > wrote:
> >> The Buildbot has detected a new failure on builder gccrust-debian-arm64
> >> while building gccrust.
> >>
On 04/08/2021 21:25, Mark Wielaard wrote:
> Hi,
>
> On Wed, Aug 04, 2021 at 03:15:00PM +, 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.wil
Hi,
On Wed, Aug 04, 2021 at 03:15:00PM +, 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/270
>
> Buil
On Fri, 2021-06-18 at 11:06 +, build...@builder.wildebeest.org
wrote:
> The Buildbot has detected a new failure on builder gccrust-fedora-
> ppc64 while building gccrust.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/61/builds/40
>
> Buildbot URL: htt
Hi,
On Sat, Jun 12, 2021 at 11:38:01PM +, 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/45
>
> Build
51 matches
Mail list logo
