Re: Regular Online GCC/Rust Meeting Time Slot

[Philip Herron]

Hello,

Thanks, for doing this I am tempted to suggest that we could have two
calls at two different time slots (one like our old time slot of
1000UTC then one later on) to allow US friends to join, I tend to work
late on Wednesdays anyway. But let's see the results of this poll I
would like to set up the call properly by tomorrow to avoid any
confusion.

Please take a moment to fill in your availability when you get a chance. Thanks.

--Phil

On Tue, 10 May 2022 at 07:21, Thomas Schwinge  wrote:
>
> Hi!
>
> We're trying to figure out a good regular online GCC/Rust meeting time
> slot.  Currently we're meeting once a month.
>
> It's been a bit difficult to find a (a) free online service that
> (b) doesn't work just with actual dates but generic days of week and
> (c) does consider different timezones...
>
> If you wish to participate in these calls, please on
>  submit your availability in a typical
> week.
>
>
> Grüße
>  Thomas
> -
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
> München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
> Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
> München, HRB 106955
> --
> Gcc-rust mailing list
> Gcc-rust@gcc.gnu.org
> https://gcc.gnu.org/mailman/listinfo/gcc-rust
-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust

☠ Buildbot (GNU Toolchain): gccrust - failed 'grep unexpected ...' (failure) (master)

[builder--- via Gcc-rust]

A new failure has been detected on builder gccrust-debian-i386 while building 
gccrust.

Full details are available at:
https://builder.sourceware.org/buildbot/#builders/27/builds/98

Build state: failed 'grep unexpected ...' (failure)
Revision: d1a2508778aafeaf19ae7e6c3e50cf9aed384854
Worker: debian-i386
Build Reason: (unknown)
Blamelist: Philip Herron , bors[bot] 
<26634292+bors[bot]@users.noreply.github.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/1/logs/stdio

- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/2/logs/stdio

- 3: configure ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/3/logs/stdio

- 4: make ( warnings )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/4/logs/stdio
- warnings (129): 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/4/logs/warnings__129_

- 5: make check ( warnings )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/5/logs/stdio
- rust.sum: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/5/logs/rust_sum
- rust.log: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/5/logs/rust_log
- warnings (1): 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/5/logs/warnings__1_

- 6: grep unexpected rust.sum ( failure )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/6/logs/stdio

- 7: prep ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/7/logs/stdio

- 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/8/logs/stdio

- 9: fetch ['../gccrs-build/gcc/config.log'] ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/9/logs/stdio

- 10: pass .bunsen.source.gitname ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/10/logs/stdio

- 11: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/11/logs/stdio

- 12: upload to bunsen ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/12/logs/stdio

- 13: clean up ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/27/builds/98/steps/13/logs/stdio

-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust

Re: ☠ Buildbot (GNU Toolchain): gccrust - failed 'grep unexpected ...' (failure) (master)

[Mark Wielaard]

On Tue, 2022-05-10 at 11:00 +, builder--- via Gcc-rust wrote:
> A new failure has been detected on builder gccrust-debian-i386 while
> building gccrust.
> 
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/27/builds/98

Just when we were all green :{

It isn't clear to me what bors is doing though. It seems to just throw
in commits randomly and then tries to fix things up with a merge
commit.

Is there any way to make bors not do that? It makes the buildbot
unhappy and makes bisecting commits really hard.

Ideally all commits are done on top of the tree without these odd merge
commits. So do a simple rebase first, then commit/push.

Cheers,

Mark
-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust

Re: ☠ Buildbot (GNU Toolchain): gccrust - failed 'grep unexpected ...' (failure) (master)

[dkm--- via Gcc-rust]

May 10, 2022 1:38 PM, "Mark Wielaard"  wrote:

> On Tue, 2022-05-10 at 11:00 +, builder--- via Gcc-rust wrote:
> 
>> A new failure has been detected on builder gccrust-debian-i386 while
>> building gccrust.
>> 
>> Full details are available at:
>> https://builder.sourceware.org/buildbot/#builders/27/builds/98
> 
> Just when we were all green :{
> 
> It isn't clear to me what bors is doing though. It seems to just throw
> in commits randomly and then tries to fix things up with a merge
> commit.
> 
> Is there any way to make bors not do that? It makes the buildbot
> unhappy and makes bisecting commits really hard.
> 
> Ideally all commits are done on top of the tree without these odd merge
> commits. So do a simple rebase first, then commit/push.
> 

I don't think that's possible. I recall reading that bors-ng handles it this 
way and you can't change this behavior. It tests everything waiting in the 
queue and only split this if tests are KO:

https://github.com/bors-ng/bors-ng

"
As commits are reviewed, bors lumps them into a queue of batches. If everything 
passes, there will just be two batches; the one that's running, and the one 
that's waiting to be run (and is accumulating more and more pull requests until 
it gets a chance to run).

To run a batch, bors creates a merge commit, merging the main branch with all 
the pull requests that make up the batch. Instead of pushing the merge commit 
immediately, however, it will instead push it to the staging branch. They'll 
look like this:

Merge #5 #7 #8

5: Rename `bifurcate()` to `bifurcateCrab()`
7: Call `bifurcate()` in the `onland` event handler
8: Fix crash in `drive()`

If the build passes, the main branch gets fast-forwarded to meet the staging 
branch. Since the main branch contains the exact contents that were just 
tested, bit-for-bit, it's not broken. (at least, not in any way that the 
automated tests are able to detect)

If the build fails, bors will follow a strategy called "bisecting". Namely, it 
splits the batch into two batches, and pushes those to the queue. In this 
example, the first batch will look like this:
...
"

:(

Marc
-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust

☠ Buildbot (GNU Toolchain): gccrust - failed 'grep unexpected ...' (failure) (master)

[builder--- via Gcc-rust]

A new failure has been detected on builder gccrust-debian-ppc64 while building 
gccrust.

Full details are available at:
https://builder.sourceware.org/buildbot/#builders/3/builds/100

Build state: failed 'grep unexpected ...' (failure)
Revision: 2959ff8e7dd8b06bee76636af84c5aee06971397
Worker: debian-ppc64
Build Reason: (unknown)
Blamelist: Arthur Cohen , bors[bot] 
<26634292+bors[bot]@users.noreply.github.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/1/logs/stdio

- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/2/logs/stdio

- 3: configure ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/3/logs/stdio

- 4: make ( warnings )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/4/logs/stdio
- warnings (32): 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/4/logs/warnings__32_

- 5: make check ( warnings )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/5/logs/stdio
- rust.sum: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/5/logs/rust_sum
- rust.log: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/5/logs/rust_log
- warnings (1): 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/5/logs/warnings__1_

- 6: grep unexpected rust.sum ( failure )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/6/logs/stdio

- 7: prep ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/7/logs/stdio

- 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/8/logs/stdio

- 9: fetch ['../gccrs-build/gcc/config.log'] ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/9/logs/stdio

- 10: pass .bunsen.source.gitname ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/10/logs/stdio

- 11: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/11/logs/stdio

- 12: upload to bunsen ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/12/logs/stdio

- 13: clean up ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/3/builds/100/steps/13/logs/stdio

A new failure has been detected on builder gccrust-fedora-s390x while building 
gccrust.

Full details are available at:
https://builder.sourceware.org/buildbot/#builders/37/builds/100

Build state: failed 'grep unexpected ...' (failure)
Revision: 2959ff8e7dd8b06bee76636af84c5aee06971397
Worker: fedora-s390x
Build Reason: (unknown)
Blamelist: Arthur Cohen , bors[bot] 
<26634292+bors[bot]@users.noreply.github.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/1/logs/stdio

- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/2/logs/stdio

- 3: configure ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/3/logs/stdio

- 4: make ( warnings )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/4/logs/stdio
- warnings (54): 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/4/logs/warnings__54_

- 5: make check ( warnings )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/5/logs/stdio
- rust.sum: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/5/logs/rust_sum
- rust.log: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/5/logs/rust_log
- warnings (4): 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/5/logs/warnings__4_

- 6: grep unexpected rust.sum ( failure )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/6/logs/stdio

- 7: prep ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/7/logs/stdio

- 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/37/builds/100/steps/8/logs/stdio

- 9: fetch ['../gccrs-build/gcc/config.log'] ( success )
Logs: