From builder@sourceware.org Mon Jul 4 09:13:12 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Mon, 04 Jul 2022 09:13:12 +0000 Subject: =?utf-8?q?=E2=98=A0_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_failed_update_=28failure=29_=28master=29?= Message-ID: <20220704091312.929733858288@sourceware.org> A new failure has been detected on builder gccrust-opensuseleap-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/104/builds/71 Build state: failed update (failure) Revision: (unknown) Worker: bb2 Build Reason: (unknown) Blamelist: David Faust , bors[bot] <26634292+bors[bot]@users.noreply.github.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/71/steps/1/logs/stdio A new failure has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/132/builds/3 Build state: failed update (failure) Revision: (unknown) Worker: bb2 Build Reason: (unknown) Blamelist: Arthur Cohen , David Faust , bors[bot] <26634292+bors[bot]@users.noreply.github.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/3/steps/1/logs/stdio From mark@klomp.org Mon Jul 4 10:26:12 2022 From: mark@klomp.org (Mark Wielaard) Date: Mon, 4 Jul 2022 12:26:12 +0200 Subject: =?utf-8?B?4pigIEJ1aWxkYm8=?= =?utf-8?Q?t?= (GNU Toolchain): gccrust - failed update (failure) (master) In-Reply-To: <20220704091312.929733858288@sourceware.org> References: <20220704091312.929733858288@sourceware.org> Message-ID: On Mon, Jul 04, 2022 at 09:13:12AM +0000, builder--- via Gcc-rust wrote: > A new failure has been detected on builder gccrust-opensuseleap-x86_64 while building gccrust. > [,,,] > A new failure has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Apologies, the builder ran out of disk space. The VM will be allocated a bit more disk after a reboot later today. Cheers, Mark From builder@sourceware.org Mon Jul 4 14:56:34 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Mon, 04 Jul 2022 14:56:34 +0000 Subject: =?utf-8?q?=E2=98=BA_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_build_successful_=28master=29?= Message-ID: <20220704145634.E068A38582A7@sourceware.org> A restored build has been detected on builder gccrust-debian-testing-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/146/builds/2 Build state: build successful Revision: fa006a67280039e0d6c6f574896bb8d819b452fe Worker: bb3 Build Reason: (unknown) Blamelist: Arthur Cohen , CohenArthur , David Faust , Faisal Abbas <90.abbasfaisal@gmail.com>, Marc Poulhi?s , Mark Wielaard , Nirmal Patel , Philip Herron , Rainer Orth , Sebastien Lacoste , Thomas Young , Zopolis4 , andrewnaguib <24280372+ndrwnaguib@users.noreply.github.com>, antego , bors[bot] <26634292+bors[bot]@users.noreply.github.com>, liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/4/logs/stdio - warnings (24): https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/4/logs/warnings__24_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/5/logs/rust_log - warnings (1): https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/5/logs/warnings__1_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/7/logs/stdio - 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/8/logs/stdio - 9: fetch ['../gccrs-build/gcc/config.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/9/logs/stdio - 10: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/10/logs/stdio - 11: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/11/logs/stdio - 12: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/12/logs/stdio - 13: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/13/logs/stdio - 14: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/2/steps/14/logs/stdio From builder@sourceware.org Mon Jul 4 14:57:31 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Mon, 04 Jul 2022 14:57:31 +0000 Subject: =?utf-8?q?=E2=98=BA_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_build_successful_=28master=29?= Message-ID: <20220704145731.999353857BB5@sourceware.org> A restored build has been detected on builder gccrust-opensuseleap-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/104/builds/72 Build state: build successful Revision: fa006a67280039e0d6c6f574896bb8d819b452fe Worker: bb2 Build Reason: (unknown) Blamelist: David Faust , 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/104/builds/72/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/4/logs/stdio - warnings (74): https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/4/logs/warnings__74_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/5/logs/rust_log - warnings (1): https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/5/logs/warnings__1_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/7/logs/stdio - 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/8/logs/stdio - 9: fetch ['../gccrs-build/gcc/config.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/9/logs/stdio - 10: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/10/logs/stdio - 11: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/11/logs/stdio - 12: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/12/logs/stdio - 13: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/13/logs/stdio - 14: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/72/steps/14/logs/stdio From builder@sourceware.org Mon Jul 4 14:58:23 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Mon, 04 Jul 2022 14:58:23 +0000 Subject: =?utf-8?q?=E2=98=BA_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_build_successful_=28master=29?= Message-ID: <20220704145823.4AA893857BB6@sourceware.org> A restored build has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/132/builds/4 Build state: build successful Revision: fa006a67280039e0d6c6f574896bb8d819b452fe Worker: bb1 Build Reason: (unknown) Blamelist: Arthur Cohen , David Faust , 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/132/builds/4/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/4/logs/stdio - warnings (28): https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/4/logs/warnings__28_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/5/logs/rust_log - warnings (7): https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/5/logs/warnings__7_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/7/logs/stdio - 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/8/logs/stdio - 9: fetch ['../gccrs-build/gcc/config.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/9/logs/stdio - 10: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/10/logs/stdio - 11: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/11/logs/stdio - 12: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/12/logs/stdio - 13: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/13/logs/stdio - 14: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/4/steps/14/logs/stdio From builder@sourceware.org Thu Jul 7 10:34:04 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Thu, 07 Jul 2022 10:34:04 +0000 Subject: =?utf-8?b?4pigIEJ1aWxkYm90IChHTlUgVG9vbGNoYWluKTogZ2NjcnVzdCAtIGZhaWxlZCAnZ3JlcCB1bmV4cGVjdGVkIC4uLicgKGZhaWx1cmUpIChtYXN0ZXIp?= Message-ID: <20220707103404.21C1B3857B99@sourceware.org> 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/214 Build state: failed 'grep unexpected ...' (failure) Revision: 1f32e5b4558126d872f455c65a94d9640a93c285 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/214/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/4/logs/stdio - warnings (32): https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/4/logs/warnings__32_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/5/logs/rust_log - warnings (1): https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/5/logs/warnings__1_ - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/7/logs/stdio - 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/8/logs/stdio - 9: fetch ['../gccrs-build/gcc/config.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/9/logs/stdio - 10: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/10/logs/stdio - 11: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/11/logs/stdio - 12: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/12/logs/stdio - 13: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/13/logs/stdio - 14: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/214/steps/14/logs/stdio A new failure has been detected on builder gccrust-fedora-ppc64le while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/19/builds/214 Build state: failed 'grep unexpected ...' (failure) Revision: 1f32e5b4558126d872f455c65a94d9640a93c285 Worker: fedora-ppc64le 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/19/builds/214/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/4/logs/stdio - warnings (35): https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/4/logs/warnings__35_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/5/logs/rust_log - warnings (5): https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/5/logs/warnings__5_ - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/7/logs/stdio - 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/8/logs/stdio - 9: fetch ['../gccrs-build/gcc/config.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/9/logs/stdio - 10: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/10/logs/stdio - 11: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/11/logs/stdio - 12: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/12/logs/stdio - 13: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/13/logs/stdio - 14: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/214/steps/14/logs/stdio From builder@sourceware.org Thu Jul 7 11:02:45 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Thu, 07 Jul 2022 11:02:45 +0000 Subject: =?utf-8?q?=E2=98=BA_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_build_successful_=28master=29?= Message-ID: <20220707110246.004013858D32@sourceware.org> A restored build has been detected on builder gccrust-debian-ppc64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/3/builds/215 Build state: build successful Revision: 143219798492864c8eff7fecbdb9257fa10bf4ec Worker: debian-ppc64 Build Reason: (unknown) Blamelist: Arthur Cohen , 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/3/builds/215/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/4/logs/stdio - warnings (32): https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/4/logs/warnings__32_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/5/logs/rust_log - warnings (1): https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/5/logs/warnings__1_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/7/logs/stdio - 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/8/logs/stdio - 9: fetch ['../gccrs-build/gcc/config.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/9/logs/stdio - 10: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/10/logs/stdio - 11: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/11/logs/stdio - 12: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/12/logs/stdio - 13: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/13/logs/stdio - 14: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/215/steps/14/logs/stdio A restored build has been detected on builder gccrust-fedora-ppc64le while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/19/builds/215 Build state: build successful Revision: 143219798492864c8eff7fecbdb9257fa10bf4ec Worker: fedora-ppc64le Build Reason: (unknown) Blamelist: Arthur Cohen , 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/19/builds/215/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/4/logs/stdio - warnings (35): https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/4/logs/warnings__35_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/5/logs/rust_log - warnings (5): https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/5/logs/warnings__5_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/7/logs/stdio - 8: fetch ['../gccrs-build/gcc/testsuite/rust/rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/8/logs/stdio - 9: fetch ['../gccrs-build/gcc/config.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/9/logs/stdio - 10: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/10/logs/stdio - 11: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/11/logs/stdio - 12: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/12/logs/stdio - 13: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/13/logs/stdio - 14: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/215/steps/14/logs/stdio From philip.herron@embecosm.com Fri Jul 8 17:31:50 2022 From: philip.herron@embecosm.com (Philip Herron) Date: Fri, 8 Jul 2022 18:31:50 +0100 Subject: Rust front-end In-Reply-To: References: Message-ID: Hi Richard Thanks for your detailed response, I took some time to figure this out myself to give a decent response. It seems like we should keep the end of the year as our goal to aim for but in the meantime see if we can split patches which affect GCC over the next month or so. We have no changes to the GCC gimple/generic IRs. Usually, when I hit something inside the GCC middle-end, the front-end is doing something wrong, which has helped keep me on a good path. Other than that we have changes to: 1. Grabbing target info using the TARGET_HOOKS interfaces in gcc/config. 2. Tweaks to selftest which was already merged last year by Arthur Cohen 3. We have some minor issues with lang.opt in the latest merge from upstream which Thomas Schwinge is working on, but I believe we can work around this if we want 4. Our compiler driver needs some cleanup which we can do in the short term to get it reviewed 5. We need to make some build changes to incorporate libcore being built by gccrs which is still WIP. As for the compile link cycle, we mostly reuse the model from the GO front-end. In Rust the "crate" is a compilation unit, which means if you have a project with multiple files, you point gccrs at a single src/source.rs, the main entry point for a library (usually lib.rs). Keywords such as "mod foo", trigger the expansion of a relative path of foo.rs like a C++ included inside a namespace. All source files are then included inside this single compilation unit. When the compilation is successful, we reuse code from the Go front-end to put custom front-end metadata into a section ".rust_export". At this point, all source files are compiled into a single object file, which can be compiled into an archive or shared library as required. To link against this, it again follows similar to Go front-end, whereby the source.rs has a declaration such as "extern crate foo"; the search code will look for foo.o or libfoo.a (I haven't tested against shared libraries yet) and grab the metadata out of it and parse it in the front-end for all the necessary information such as types, public functions and generics, etc., so we can compile any imports correctly and emit the correct mangled symbols for linking. Given we are still working on this I think we can try to line up all the other GCC relating pieces for review over the summer, do we send this as usual to gcc-patches? Again thanks to everyone for helping me navigate this and answering my questions. --Phil On Tue, 28 Jun 2022 at 08:30, Richard Biener wrote: > > On Mon, Jun 27, 2022 at 4:52 PM Philip Herron > wrote: > > > > Hi everyone, > > > > Since November 2020, I've worked full-time on the Rust front-end for > > GCC, thanks to Open Source Security, Inc and Embecosm. As a result, I > > am writing to this mailing list to seek feedback from the collective > > experience here early to plan a path for upstreaming the front-end > > into GCC. > > > > 1. What is the actual process of merging a prominent feature like this upstream > > - How do we review this? > > - Do we create a "mega-commit" patch > > - How long should we expect this review process to take > > - Is there anything we can do to make this easier? > > Usually a new frontend is first proposed for merge and generally approved > by the steering committee (which should also sort out legal issues). > > For the actual review process it's best to consult previous frontend > merges - the most recent merged frontend was the D frontend and the > modula2 frontend is in the process of being reviewed. > > To be able to focus on the possibly controversical pieces separating > out changes to the generic GCC code base (such as driver or > even middle-end) should be separated out. > > It would also be helpful to provide an overview of how a rust > compile + link cycle works through the pieces in GCC (see the > modula-2 case where that involved creating stub C++ code, > compiling and linking that and how this is now done much > more straight-forward). > > > 2. What sort of quality does the GCC community expect? > > - I think it is essential that we can compile valid test cases from > > a testsuite and real projects before merging. > > - It seems reasonable that our error handling may not be 100% but be > > expected to improve over time > > - Upon merging, can features like Rust be marked as experimental > > Rust can be marked as experimental, sure. It would be not enabled > to be built by default (and you can have a whitelist of supported targets). > The most important part would be that the build works when enabled > and that most of the existing testsuite passes so it can be used to > regression test middle-end changes. > > If it is not useful at all for (basic) real-world usage then it might be not > ready yet. > > > 3. How do GCC releases work? > > - If you miss a window can we still merge code into the front-end? > > - Can we merge without a borrow checker and backport this in the future? > > The rust frontend will not be part of the release critical pieces of the > compiler (which includes the C and C++ frontends plus the set of > primary and secondary targets) so it is up to the maintainers to decide > what to merge and when. Release managers will generally ignore > issues in Rust. > > > 4. What about the possibility of merging sooner rather than later, > > which would help the project gain interest through the increased > > visibility of it as part of the GCC family. > > - Does this still allow for development churn, or will it cause friction? > > The parts where GCC and Rust overlap still need to be reviewed and > _some_ usability for users should be provided. > > > 5. Does anyone have prior experience or advice they could give us? > > I suppose Ian (for the Go frontend) or Iain (for the D frontend) can give > you hints. > > > For some context, my current project plan brings us to November 2022 > > where we (unexpected events permitting) should be able to support > > valid Rust code targeting Rustc version ~1.40 and reuse libcore, > > liballoc and libstd. This date does not account for the borrow checker > > feature and the proc macro crate, which we have a plan to implement, > > but this will be a further six-month project. > > > > Regarding patch management, we currently do our development on GitHub: > > https://github.com/Rust-GCC/gccrs; this means we can integrate our > > issue tracking with the official Rust project by linking back to the > > official Rust project's RFC issues, for example. The downside is that > > when someone uses our compiler and hits an ICE, they will be directed > > to the GCC Bugzilla, which is correct but can lead to a mismatch in > > issue tracking. Nevertheless, I think it's essential to have the > > GitHub link here to integrate with the broader Rust community. I > > believe we can triage Rust issues on the Bugzilla and raise associated > > ones on Github to manage this. > > > > From my perspective as the lead on this front-end, we are currently > > under heavy development, so this means a fair amount of code churn > > still, and I don't see this changing until we can successfully compile > > the libcore crate later this year. Although I would love to see us > > merged into GCC 13, I want to make sure this project is a success for > > everyone, and this might mean pushing back to the next release window > > to make sure this is manageable to produce a quality front-end to sit > > alongside the others. > > If you want to target GCC 13 for experimental Rust support I suggest to > get review on the overall design (where it touches GCC) and the changes > necessary to driver and build changes. The core frontend itself will usually > only get review on the parts that interface to the middle-end (thus > GENERIC code generation and language hooks). Dropping in the frontend > during Stage3 (thus until the end of the year) should be possible, especially > if the driver and build changes have been reviewed already. > > Richard. > > > I wish to thank you those in the GCC developer community, who have > > inspired me and helped me navigate my journey to this point in time. > > > > - Thomas Schwinge > > - Mark Wielaard > > - Tom Tromey > > - Ian Lance Taylor > > - David Edelsohn > > - David Malcolm > > - Martin Jambor > > > > Thanks > > > > ?Phil From richard.guenther@gmail.com Mon Jul 11 07:50:21 2022 From: richard.guenther@gmail.com (Richard Biener) Date: Mon, 11 Jul 2022 09:50:21 +0200 Subject: Rust front-end In-Reply-To: References: Message-ID: On Fri, Jul 8, 2022 at 7:32 PM Philip Herron wrote: > > Hi Richard > > Thanks for your detailed response, I took some time to figure this out > myself to give a decent response. It seems like we should keep the end > of the year as our goal to aim for but in the meantime see if we can > split patches which affect GCC over the next month or so. We have no > changes to the GCC gimple/generic IRs. Usually, when I hit something > inside the GCC middle-end, the front-end is doing something wrong, > which has helped keep me on a good path. Other than that we have > changes to: > > 1. Grabbing target info using the TARGET_HOOKS interfaces in gcc/config. > 2. Tweaks to selftest which was already merged last year by Arthur Cohen > 3. We have some minor issues with lang.opt in the latest merge from > upstream which Thomas Schwinge is working on, but I believe we can > work around this if we want > 4. Our compiler driver needs some cleanup which we can do in the short > term to get it reviewed > 5. We need to make some build changes to incorporate libcore being > built by gccrs which is still WIP. > > As for the compile link cycle, we mostly reuse the model from the GO > front-end. In Rust the "crate" is a compilation unit, which means if > you have a project with multiple files, you point gccrs at a single > src/source.rs, the main entry point for a library (usually lib.rs). > Keywords such as "mod foo", trigger the expansion of a relative path > of foo.rs like a C++ included inside a namespace. All source files are > then included inside this single compilation unit. When the > compilation is successful, we reuse code from the Go front-end to put > custom front-end metadata into a section ".rust_export". At this > point, all source files are compiled into a single object file, which > can be compiled into an archive or shared library as required. To link > against this, it again follows similar to Go front-end, whereby the > source.rs has a declaration such as "extern crate foo"; the search > code will look for foo.o or libfoo.a (I haven't tested against shared > libraries yet) and grab the metadata out of it and parse it in the > front-end for all the necessary information such as types, public > functions and generics, etc., so we can compile any imports correctly > and emit the correct mangled symbols for linking. > > Given we are still working on this I think we can try to line up all > the other GCC relating pieces for review over the summer, do we send > this as usual to gcc-patches? Yes, that's the prefered way. Having an integration branch ready for people to play with is also useful - if you are ready you might want to push something like that to the gcc.gnu.org repository under the devel/ namespace. Thanks, Richard. > Again thanks to everyone for helping me navigate this and answering my > questions. > > --Phil > > On Tue, 28 Jun 2022 at 08:30, Richard Biener wrote: > > > > On Mon, Jun 27, 2022 at 4:52 PM Philip Herron > > wrote: > > > > > > Hi everyone, > > > > > > Since November 2020, I've worked full-time on the Rust front-end for > > > GCC, thanks to Open Source Security, Inc and Embecosm. As a result, I > > > am writing to this mailing list to seek feedback from the collective > > > experience here early to plan a path for upstreaming the front-end > > > into GCC. > > > > > > 1. What is the actual process of merging a prominent feature like this upstream > > > - How do we review this? > > > - Do we create a "mega-commit" patch > > > - How long should we expect this review process to take > > > - Is there anything we can do to make this easier? > > > > Usually a new frontend is first proposed for merge and generally approved > > by the steering committee (which should also sort out legal issues). > > > > For the actual review process it's best to consult previous frontend > > merges - the most recent merged frontend was the D frontend and the > > modula2 frontend is in the process of being reviewed. > > > > To be able to focus on the possibly controversical pieces separating > > out changes to the generic GCC code base (such as driver or > > even middle-end) should be separated out. > > > > It would also be helpful to provide an overview of how a rust > > compile + link cycle works through the pieces in GCC (see the > > modula-2 case where that involved creating stub C++ code, > > compiling and linking that and how this is now done much > > more straight-forward). > > > > > 2. What sort of quality does the GCC community expect? > > > - I think it is essential that we can compile valid test cases from > > > a testsuite and real projects before merging. > > > - It seems reasonable that our error handling may not be 100% but be > > > expected to improve over time > > > - Upon merging, can features like Rust be marked as experimental > > > > Rust can be marked as experimental, sure. It would be not enabled > > to be built by default (and you can have a whitelist of supported targets). > > The most important part would be that the build works when enabled > > and that most of the existing testsuite passes so it can be used to > > regression test middle-end changes. > > > > If it is not useful at all for (basic) real-world usage then it might be not > > ready yet. > > > > > 3. How do GCC releases work? > > > - If you miss a window can we still merge code into the front-end? > > > - Can we merge without a borrow checker and backport this in the future? > > > > The rust frontend will not be part of the release critical pieces of the > > compiler (which includes the C and C++ frontends plus the set of > > primary and secondary targets) so it is up to the maintainers to decide > > what to merge and when. Release managers will generally ignore > > issues in Rust. > > > > > 4. What about the possibility of merging sooner rather than later, > > > which would help the project gain interest through the increased > > > visibility of it as part of the GCC family. > > > - Does this still allow for development churn, or will it cause friction? > > > > The parts where GCC and Rust overlap still need to be reviewed and > > _some_ usability for users should be provided. > > > > > 5. Does anyone have prior experience or advice they could give us? > > > > I suppose Ian (for the Go frontend) or Iain (for the D frontend) can give > > you hints. > > > > > For some context, my current project plan brings us to November 2022 > > > where we (unexpected events permitting) should be able to support > > > valid Rust code targeting Rustc version ~1.40 and reuse libcore, > > > liballoc and libstd. This date does not account for the borrow checker > > > feature and the proc macro crate, which we have a plan to implement, > > > but this will be a further six-month project. > > > > > > Regarding patch management, we currently do our development on GitHub: > > > https://github.com/Rust-GCC/gccrs; this means we can integrate our > > > issue tracking with the official Rust project by linking back to the > > > official Rust project's RFC issues, for example. The downside is that > > > when someone uses our compiler and hits an ICE, they will be directed > > > to the GCC Bugzilla, which is correct but can lead to a mismatch in > > > issue tracking. Nevertheless, I think it's essential to have the > > > GitHub link here to integrate with the broader Rust community. I > > > believe we can triage Rust issues on the Bugzilla and raise associated > > > ones on Github to manage this. > > > > > > From my perspective as the lead on this front-end, we are currently > > > under heavy development, so this means a fair amount of code churn > > > still, and I don't see this changing until we can successfully compile > > > the libcore crate later this year. Although I would love to see us > > > merged into GCC 13, I want to make sure this project is a success for > > > everyone, and this might mean pushing back to the next release window > > > to make sure this is manageable to produce a quality front-end to sit > > > alongside the others. > > > > If you want to target GCC 13 for experimental Rust support I suggest to > > get review on the overall design (where it touches GCC) and the changes > > necessary to driver and build changes. The core frontend itself will usually > > only get review on the parts that interface to the middle-end (thus > > GENERIC code generation and language hooks). Dropping in the frontend > > during Stage3 (thus until the end of the year) should be possible, especially > > if the driver and build changes have been reviewed already. > > > > Richard. > > > > > I wish to thank you those in the GCC developer community, who have > > > inspired me and helped me navigate my journey to this point in time. > > > > > > - Thomas Schwinge > > > - Mark Wielaard > > > - Tom Tromey > > > - Ian Lance Taylor > > > - David Edelsohn > > > - David Malcolm > > > - Martin Jambor > > > > > > Thanks > > > > > > ?Phil From dje.gcc@gmail.com Mon Jul 11 15:01:44 2022 From: dje.gcc@gmail.com (David Edelsohn) Date: Mon, 11 Jul 2022 11:01:44 -0400 Subject: Rust front-end In-Reply-To: References: Message-ID: On Mon, Jun 27, 2022 at 10:52 AM Philip Herron wrote: > > Hi everyone, > > Since November 2020, I've worked full-time on the Rust front-end for > GCC, thanks to Open Source Security, Inc and Embecosm. As a result, I > am writing to this mailing list to seek feedback from the collective > experience here early to plan a path for upstreaming the front-end > into GCC. > > 1. What is the actual process of merging a prominent feature like this upstream > - How do we review this? > - Do we create a "mega-commit" patch > - How long should we expect this review process to take > - Is there anything we can do to make this easier? > > 2. What sort of quality does the GCC community expect? > - I think it is essential that we can compile valid test cases from > a testsuite and real projects before merging. > - It seems reasonable that our error handling may not be 100% but be > expected to improve over time > - Upon merging, can features like Rust be marked as experimental > > 3. How do GCC releases work? > - If you miss a window can we still merge code into the front-end? > - Can we merge without a borrow checker and backport this in the future? > > 4. What about the possibility of merging sooner rather than later, > which would help the project gain interest through the increased > visibility of it as part of the GCC family. > - Does this still allow for development churn, or will it cause friction? > > 5. Does anyone have prior experience or advice they could give us? > > For some context, my current project plan brings us to November 2022 > where we (unexpected events permitting) should be able to support > valid Rust code targeting Rustc version ~1.40 and reuse libcore, > liballoc and libstd. This date does not account for the borrow checker > feature and the proc macro crate, which we have a plan to implement, > but this will be a further six-month project. > > Regarding patch management, we currently do our development on GitHub: > https://github.com/Rust-GCC/gccrs; this means we can integrate our > issue tracking with the official Rust project by linking back to the > official Rust project's RFC issues, for example. The downside is that > when someone uses our compiler and hits an ICE, they will be directed > to the GCC Bugzilla, which is correct but can lead to a mismatch in > issue tracking. Nevertheless, I think it's essential to have the > GitHub link here to integrate with the broader Rust community. I > believe we can triage Rust issues on the Bugzilla and raise associated > ones on Github to manage this. > > From my perspective as the lead on this front-end, we are currently > under heavy development, so this means a fair amount of code churn > still, and I don't see this changing until we can successfully compile > the libcore crate later this year. Although I would love to see us > merged into GCC 13, I want to make sure this project is a success for > everyone, and this might mean pushing back to the next release window > to make sure this is manageable to produce a quality front-end to sit > alongside the others. > > I wish to thank you those in the GCC developer community, who have > inspired me and helped me navigate my journey to this point in time. > > - Thomas Schwinge > - Mark Wielaard > - Tom Tromey > - Ian Lance Taylor > - David Edelsohn > - David Malcolm > - Martin Jambor Congratulations! The GCC Steering Committee has voted to accept the contribution of the Rust Frontend (aka GCC Rust) to GCC. Please work with the GCC Global Reviewers and GCC Release Managers for technical review and technical approval of the patches. We look forward to including a preliminary, beta version of GCC Rust in GCC 13 as a non-default language. Thanks, David From philip.herron@embecosm.com Wed Jul 13 16:45:48 2022 From: philip.herron@embecosm.com (philip.herron@embecosm.com) Date: Wed, 13 Jul 2022 16:45:48 +0000 Subject: Cancelled event with note: GCC Rust hang out @ Wed 13 Jul 2022 7pm - 7:30pm (BST) (gcc-rust@gcc.gnu.org) Message-ID: <0000000000006aea3f05e3b28443@google.com> This event has been cancelled with a note: "Out of office" GCC Rust hang out Wednesday 13 Jul 2022 ? 7pm ? 7:30pm United Kingdom Time Location https://meet.jit.si/gccrs-community-call https://www.google.com/url?q=https%3A%2F%2Fmeet.jit.si%2Fgccrs-community-call&sa=D&ust=1658162700000000&usg=AOvVaw3aCEpU8qTt2CP0KDF1i6CX Hi everyone This is a regular call for anyone to drop in and talk about gccrs, it should suit some people better with this time. We will reuse our jitsi link: https://meet.jit.si/gccrs-community-call Thanks --Phil Organiser philip.herron@embecosm.com philip.herron@embecosm.com Guests philip.herron@embecosm.com- organiser gcc-rust@gcc.gnu.org ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee of the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organiser, be added to the guest list, invite others regardless of their own invitation status or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1487 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1534 bytes Desc: not available URL: From builder@sourceware.org Fri Jul 15 17:46:42 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Fri, 15 Jul 2022 17:46:42 +0000 Subject: =?utf-8?b?4pigIEJ1aWxkYm90IChHTlUgVG9vbGNoYWluKTogZ2NjcnVzdCAtIGZhaWxlZCAnZ3JlcCB1bmV4cGVjdGVkIC4uLicgKGZhaWx1cmUpIChtYXN0ZXIp?= Message-ID: <20220715174642.02F303857BBF@sourceware.org> A new failure has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/132/builds/38 Build state: failed 'grep unexpected ...' (failure) Revision: 2d1378f7310be651e2a538f192d385b136b3d697 Worker: bb2 Build Reason: (unknown) Blamelist: Philip Herron Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/4/logs/stdio - warnings (28): https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/4/logs/warnings__28_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/rust_log - warnings (8): https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/warnings__8_ - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/15/logs/stdio From mark@klomp.org Fri Jul 15 19:18:25 2022 From: mark@klomp.org (Mark Wielaard) Date: Fri, 15 Jul 2022 21:18:25 +0200 Subject: =?utf-8?B?4pigIEJ1aWxkYm90IChHTlUgVG9v?= =?utf-8?Q?lchain=29?= =?utf-8?Q?=3A?= gccrust - failed 'grep unexpected ...' (failure) (master) In-Reply-To: <20220715174642.02F303857BBF@sourceware.org> References: <20220715174642.02F303857BBF@sourceware.org> Message-ID: Hi, On Fri, Jul 15, 2022 at 05:46:42PM +0000, builder--- via Gcc-rust wrote: > A new failure has been detected on builder gccrust-rawhide-x86_64 while building gccrust. > > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/132/builds/38 > > Build state: failed 'grep unexpected ...' (failure) > Revision: 2d1378f7310be651e2a538f192d385b136b3d697 > Worker: bb2 > Build Reason: (unknown) > Blamelist: Philip Herron > > Steps: > > - 5: make check ( warnings ) > Logs: > - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/stdio > - rust.sum: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/rust_sum > - rust.log: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/rust_log > - warnings (8): https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/warnings__8_ Oddly the rust.log doesn't contain the FAILed tests. > - 14: upload to bunsen ( success ) > Logs: > - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/14/logs/stdio Luckily the upload does contain the bunsen link: https://builder.sourceware.org/testrun/4089d04b3ec71f873716bdac207b31ec43a1e00e Which contain the full rust.log file (under filelist): https://builder.sourceware.org/testrun/4089d04b3ec71f873716bdac207b31ec43a1e00e?filename=gcc%2Ftestsuite%2Frust%2Frust.log PASS: rust/execute/torture/match1.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test PASS: rust/execute/torture/match1.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none output pattern test Executing on host: /home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs-build/gcc/testsuite/rust1/../../gccrs -B/home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs-build/gcc/testsuite/rust1/../../ /home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs/gcc/testsuite/rust/execute/torture/match1.rs -fdiagnostics-plain-output -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -lm -o ./match1.exe (timeout = 10) spawn -ignore SIGHUP /home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs-build/gcc/testsuite/rust1/../../gccrs -B/home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs-build/gcc/testsuite/rust1/../../ /home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs/gcc/testsuite/rust/execute/torture/match1.rs -fdiagnostics-plain-output -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -lm -o ./match1.exe WARNING: program timed out compiler exited with status 1 FAIL: rust/execute/torture/match1.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) Excess errors: exit status is 1 Setting LD_LIBRARY_PATH to .:.: Execution timeout is: 300 FAIL: rust/execute/torture/match1.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test This is odd. The -fno-fat-lto-objects variant is the only failure. But other builds with -fno-fat-lto-objects PASS: https://builder.sourceware.org/testrun/4089d04b3ec71f873716bdac207b31ec43a1e00e?dgexpfile=rust%2Fexecute%2Ftorture%2Fexecute.exp Also all other arches/distros passed (except s390x of course): https://builder.sourceware.org/buildbot/#/changes/3381 The rawhide builder should not really be slower than other builders. So I am not sure why it timed out but others didn't. Cheers, Mark From builder@sourceware.org Sun Jul 17 20:47:38 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Sun, 17 Jul 2022 20:47:38 +0000 Subject: =?utf-8?q?=E2=98=BA_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_build_successful_=28master=29?= Message-ID: <20220717204738.7CF5E3857BA3@sourceware.org> A restored build has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/132/builds/39 Build state: build successful Revision: 9c7a580aa13707a18c53bc772c3d9301dd9bfb2c Worker: bb2 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/132/builds/39/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/4/logs/stdio - warnings (28): https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/4/logs/warnings__28_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/5/logs/rust_log - warnings (7): https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/5/logs/warnings__7_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/39/steps/15/logs/stdio From philip.herron@embecosm.com Wed Jul 20 15:17:02 2022 From: philip.herron@embecosm.com (philip.herron@embecosm.com) Date: Wed, 20 Jul 2022 15:17:02 +0000 Subject: Cancelled event: GCC Rust hang out @ Wed 20 Jul 2022 7pm - 7:30pm (BST) (gcc-rust@gcc.gnu.org) Message-ID: <000000000000d7fd8505e43e17fb@google.com> This event has been cancelled. GCC Rust hang out Wednesday 20 Jul 2022 ? 7pm ? 7:30pm United Kingdom Time Location https://meet.jit.si/gccrs-community-call https://www.google.com/url?q=https%3A%2F%2Fmeet.jit.si%2Fgccrs-community-call&sa=D&ust=1658762220000000&usg=AOvVaw2k9mvAib8c9uaaRS3P8sUU Hi everyone This is a regular call for anyone to drop in and talk about gccrs, it should suit some people better with this time. We will reuse our jitsi link: https://meet.jit.si/gccrs-community-call Thanks --Phil Organiser philip.herron@embecosm.com philip.herron@embecosm.com Guests philip.herron@embecosm.com- organiser gcc-rust@gcc.gnu.org ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee of the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organiser, be added to the guest list, invite others regardless of their own invitation status or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1487 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1534 bytes Desc: not available URL: From builder@sourceware.org Thu Jul 21 22:38:18 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Thu, 21 Jul 2022 22:38:18 +0000 Subject: =?utf-8?q?=E2=98=A0_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_failed_=27make_clean=27_=28failure=29_=28master=29?= Message-ID: <20220721223818.B15B538356A7@sourceware.org> A new failure has been detected on builder gccrust-bootstrap-debian-amd64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/107/builds/43 Build state: failed 'make clean' (failure) Revision: 51f03d9d697b0f3fed65f85e88ce41d424c844fb Worker: bb2 Build Reason: (unknown) Blamelist: Thomas Schwinge Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/4/logs/stdio - warnings (42): https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/4/logs/warnings__42_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/5/logs/rust_log - warnings (1): https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/5/logs/warnings__1_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/15/logs/stdio - 16: make clean ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/16/logs/stdio From mark@klomp.org Thu Jul 21 22:49:54 2022 From: mark@klomp.org (Mark Wielaard) Date: Fri, 22 Jul 2022 00:49:54 +0200 Subject: =?utf-8?Q?=E2=98=A0_Buildbot_=28GN?= =?utf-8?Q?U?= Toolchain): gccrust - failed 'make clean' (failure) (master) In-Reply-To: <20220721223818.B15B538356A7@sourceware.org> References: <20220721223818.B15B538356A7@sourceware.org> Message-ID: Hi, On Thu, Jul 21, 2022 at 10:38:18PM +0000, builder--- via Gcc-rust wrote: > A new failure has been detected on builder gccrust-bootstrap-debian-amd64 while building gccrust. > > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/107/builds/43 > > Build state: failed 'make clean' (failure) > Revision: 51f03d9d697b0f3fed65f85e88ce41d424c844fb > Worker: bb2 > Build Reason: (unknown) > Blamelist: Thomas Schwinge > > Steps: > [...] > - 16: make clean ( failure ) > Logs: > - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/16/logs/stdio Sorry, this was supposed to simply be to save some space at the end of the build: https://sourceware.org/pipermail/buildbot/2022q3/000162.html Apparently make clean doesn't work as expected. I will try to look into it, but it might take one or two days till I have time. Apologies for the mess. Cheers, Mark From builder@sourceware.org Fri Jul 22 11:58:12 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Fri, 22 Jul 2022 11:58:12 +0000 Subject: =?utf-8?b?4pigIEJ1aWxkYm90IChHTlUgVG9vbGNoYWluKTogZ2NjcnVzdCAtIGZhaWxlZCAnZ3JlcCB1bmV4cGVjdGVkIC4uLicgKGZhaWx1cmUpIChtYXN0ZXIp?= Message-ID: <20220722115812.7B0273835696@sourceware.org> 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/253 Build state: failed 'grep unexpected ...' (failure) Revision: 0340a567fedab5f902febcea8f415943ca85b330 Worker: debian-ppc64 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/4/logs/stdio - warnings (32): https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/4/logs/warnings__32_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/253/steps/16/logs/stdio A new failure has been detected on builder gccrust-fedora-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/16/builds/259 Build state: failed 'grep unexpected ...' (failure) Revision: 0340a567fedab5f902febcea8f415943ca85b330 Worker: bb1 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/4/logs/stdio - warnings (28): https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/4/logs/warnings__28_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/5/logs/rust_log - warnings (6): https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/5/logs/warnings__6_ - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/259/steps/16/logs/stdio A new failure has been detected on builder gccrust-fedora-ppc64le while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/19/builds/252 Build state: failed 'grep unexpected ...' (failure) Revision: 0340a567fedab5f902febcea8f415943ca85b330 Worker: fedora-ppc64le Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/4/logs/stdio - warnings (35): https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/4/logs/warnings__35_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/5/logs/rust_log - warnings (4): https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/5/logs/warnings__4_ - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/252/steps/16/logs/stdio 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/252 Build state: failed 'grep unexpected ...' (failure) Revision: 0340a567fedab5f902febcea8f415943ca85b330 Worker: debian-i386 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/4/logs/stdio - warnings (50): https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/4/logs/warnings__50_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/252/steps/16/logs/stdio A new failure has been detected on builder gccrust-opensusetw-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/103/builds/115 Build state: failed 'grep unexpected ...' (failure) Revision: 0340a567fedab5f902febcea8f415943ca85b330 Worker: bb1 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/4/logs/stdio - warnings (27): https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/4/logs/warnings__27_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/115/steps/16/logs/stdio A new failure has been detected on builder gccrust-opensuseleap-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/104/builds/116 Build state: failed 'grep unexpected ...' (failure) Revision: 0340a567fedab5f902febcea8f415943ca85b330 Worker: bb1 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/4/logs/stdio - warnings (74): https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/4/logs/warnings__74_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/116/steps/16/logs/stdio A new failure has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/132/builds/48 Build state: failed 'grep unexpected ...' (failure) Revision: 0340a567fedab5f902febcea8f415943ca85b330 Worker: bb1 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/4/logs/stdio - warnings (28): https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/4/logs/warnings__28_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/5/logs/rust_log - warnings (6): https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/5/logs/warnings__6_ - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/48/steps/16/logs/stdio A new failure has been detected on builder gccrust-debian-testing-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/146/builds/46 Build state: failed 'grep unexpected ...' (failure) Revision: 0340a567fedab5f902febcea8f415943ca85b330 Worker: bb1 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/4/logs/stdio - warnings (24): https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/4/logs/warnings__24_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/46/steps/16/logs/stdio A new failure has been detected on builder gccrust-fedora-arm64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/179/builds/22 Build state: failed 'grep unexpected ...' (failure) Revision: 0340a567fedab5f902febcea8f415943ca85b330 Worker: fedora-arm64 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/4/logs/stdio - warnings (36): https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/4/logs/warnings__36_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/5/logs/rust_log - warnings (6): https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/5/logs/warnings__6_ - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/22/steps/16/logs/stdio From builder@sourceware.org Fri Jul 22 12:03:47 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Fri, 22 Jul 2022 12:03:47 +0000 Subject: =?utf-8?q?=E2=98=BA_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_build_successful_=28master=29?= Message-ID: <20220722120347.1496A38356BF@sourceware.org> A restored build has been detected on builder gccrust-debian-ppc64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/3/builds/254 Build state: build successful Revision: 3ce22036e48a4f8805440abcd291ecd35d2ca468 Worker: debian-ppc64 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/4/logs/stdio - warnings (32): https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/4/logs/warnings__32_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/254/steps/16/logs/stdio A restored build has been detected on builder gccrust-fedora-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/16/builds/260 Build state: build successful Revision: 3ce22036e48a4f8805440abcd291ecd35d2ca468 Worker: bb2 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/4/logs/stdio - warnings (28): https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/4/logs/warnings__28_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/5/logs/rust_log - warnings (6): https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/5/logs/warnings__6_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/16/builds/260/steps/16/logs/stdio A restored build has been detected on builder gccrust-fedora-ppc64le while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/19/builds/253 Build state: build successful Revision: 3ce22036e48a4f8805440abcd291ecd35d2ca468 Worker: fedora-ppc64le Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/4/logs/stdio - warnings (35): https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/4/logs/warnings__35_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/5/logs/rust_log - warnings (4): https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/5/logs/warnings__4_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/253/steps/16/logs/stdio A restored build has been detected on builder gccrust-debian-i386 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/27/builds/253 Build state: build successful Revision: 3ce22036e48a4f8805440abcd291ecd35d2ca468 Worker: debian-i386-2 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/4/logs/stdio - warnings (50): https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/4/logs/warnings__50_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/253/steps/16/logs/stdio A restored build has been detected on builder gccrust-opensusetw-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/103/builds/116 Build state: build successful Revision: 3ce22036e48a4f8805440abcd291ecd35d2ca468 Worker: bb1 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/4/logs/stdio - warnings (27): https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/4/logs/warnings__27_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/103/builds/116/steps/16/logs/stdio A restored build has been detected on builder gccrust-opensuseleap-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/104/builds/117 Build state: build successful Revision: 3ce22036e48a4f8805440abcd291ecd35d2ca468 Worker: bb3 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/4/logs/stdio - warnings (74): https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/4/logs/warnings__74_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/104/builds/117/steps/16/logs/stdio A restored build has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/132/builds/49 Build state: build successful Revision: 3ce22036e48a4f8805440abcd291ecd35d2ca468 Worker: bb2 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/4/logs/stdio - warnings (28): https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/4/logs/warnings__28_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/5/logs/rust_log - warnings (6): https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/5/logs/warnings__6_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/49/steps/16/logs/stdio A restored build has been detected on builder gccrust-debian-testing-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/146/builds/47 Build state: build successful Revision: 3ce22036e48a4f8805440abcd291ecd35d2ca468 Worker: bb1 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/4/logs/stdio - warnings (24): https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/4/logs/warnings__24_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/146/builds/47/steps/16/logs/stdio A restored build has been detected on builder gccrust-fedora-arm64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/179/builds/23 Build state: build successful Revision: 3ce22036e48a4f8805440abcd291ecd35d2ca468 Worker: fedora-arm64 Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/4/logs/stdio - warnings (36): https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/4/logs/warnings__36_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/5/logs/rust_log - warnings (6): https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/5/logs/warnings__6_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/179/builds/23/steps/16/logs/stdio From mark@klomp.org Fri Jul 22 14:48:18 2022 From: mark@klomp.org (Mark Wielaard) Date: Fri, 22 Jul 2022 16:48:18 +0200 Subject: =?utf-8?Q?=E2=98=A0_Buildbot_=28GN?= =?utf-8?Q?U?= Toolchain): gccrust - failed 'make clean' (failure) (master) In-Reply-To: References: <20220721223818.B15B538356A7@sourceware.org> Message-ID: <20220722144818.GA27274@gnu.wildebeest.org> Hi, On Fri, Jul 22, 2022 at 12:49:54AM +0200, Mark Wielaard wrote: > On Thu, Jul 21, 2022 at 10:38:18PM +0000, builder--- via Gcc-rust wrote: > > A new failure has been detected on builder gccrust-bootstrap-debian-amd64 while building gccrust. > > > > Full details are available at: > > https://builder.sourceware.org/buildbot/#builders/107/builds/43 > > > > Build state: failed 'make clean' (failure) > > Revision: 51f03d9d697b0f3fed65f85e88ce41d424c844fb > > Worker: bb2 > > Build Reason: (unknown) > > Blamelist: Thomas Schwinge > > > > Steps: > > [...] > > - 16: make clean ( failure ) > > Logs: > > - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/16/logs/stdio > > Sorry, this was supposed to simply be to save some space at the end > of the build: > https://sourceware.org/pipermail/buildbot/2022q3/000162.html > > Apparently make clean doesn't work as expected. I will try to look > into it, but it might take one or two days till I have > time. Apologies for the mess. It only happens after a boostrap build. But I couldn't really figure out what is going wrong. It looks like some parts of make clean require bash while the debian-stable tester uses dash as default. For now I just remove the whole build tree at the end instead of running make clean. Cheers, Mark -------------- next part -------------- >From f2db122660f2f03632253493dd7ae801e9567056 Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Fri, 22 Jul 2022 16:39:58 +0200 Subject: [PATCH] Don't make clean after a gccrs bootstrap It looks like after a bootstrap make clean gets confused. Just blow away the whole builddir when we are done with it. --- builder/master.cfg | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/builder/master.cfg b/builder/master.cfg index 2047eaa..0d94e67 100644 --- a/builder/master.cfg +++ b/builder/master.cfg @@ -1686,7 +1686,10 @@ gccrust_bootstrap_factory.addStep(gccrust_make_bootstrap_step) gccrust_bootstrap_factory.addStep(gccrust_check_bootstrap_step) gccrust_bootstrap_factory.addStep(gccrust_check_check_step) gccrust_bootstrap_factory.addSteps(gccrust_bunsen_steps) -gccrust_bootstrap_factory.addStep(gccrust_make_clean_step) +# It looks like after a bootstrap make clean gets confused +# Just blow away the whole builddir when we are done with it +#gccrust_bootstrap_factory.addStep(gccrust_make_clean_step) +gccrust_bootstrap_factory.addStep(gccrust_rm_build_step) gccrust_fedora_x86_64_builder = util.BuilderConfig( name="gccrust-fedora-x86_64", -- 2.31.1 From builder@sourceware.org Wed Jul 27 14:21:33 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Wed, 27 Jul 2022 14:21:33 +0000 Subject: =?utf-8?q?=E2=98=BA_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_build_successful_=28master=29?= Message-ID: <20220727142133.412623857366@sourceware.org> A restored build has been detected on builder gccrust-bootstrap-debian-amd64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/107/builds/48 Build state: build successful Revision: 961468ed824a7b49f10ed597ba9dcc98177125ca Worker: bb2 Build Reason: (unknown) Blamelist: Arthur Cohen , bors[bot] <26634292+bors[bot]@users.noreply.github.com>, liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/4/logs/stdio - warnings (42): https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/4/logs/warnings__42_ - 5: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/7/logs/stdio - 8: build bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/8/logs/stdio - 9: fetch bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/9/logs/stdio - 10: unpack bunsen.cpio ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/15/logs/stdio - 16: rm -rf gccrs-build_1 ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/48/steps/16/logs/stdio From philip.herron@embecosm.com Wed Jul 27 15:48:47 2022 From: philip.herron@embecosm.com (philip.herron@embecosm.com) Date: Wed, 27 Jul 2022 15:48:47 +0000 Subject: Cancelled event: GCC Rust hang out @ Wed 27 Jul 2022 7pm - 7:30pm (BST) (gcc-rust@gcc.gnu.org) Message-ID: <00000000000047334705e4cb5a36@google.com> This event has been cancelled. GCC Rust hang out Wednesday 27 Jul 2022 ? 7pm ? 7:30pm United Kingdom Time Location https://meet.jit.si/gccrs-community-call https://www.google.com/url?q=https%3A%2F%2Fmeet.jit.si%2Fgccrs-community-call&sa=D&ust=1659368880000000&usg=AOvVaw1C2RmCoexGXDTiqYI03GDO Hi everyone This is a regular call for anyone to drop in and talk about gccrs, it should suit some people better with this time. We will reuse our jitsi link: https://meet.jit.si/gccrs-community-call Thanks --Phil Organiser philip.herron@embecosm.com philip.herron@embecosm.com Guests philip.herron@embecosm.com- organiser gcc-rust@gcc.gnu.org ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee of the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organiser, be added to the guest list, invite others regardless of their own invitation status or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1487 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1534 bytes Desc: not available URL: From thomas@codesourcery.com Fri Jul 29 09:29:03 2022 From: thomas@codesourcery.com (Thomas Schwinge) Date: Fri, 29 Jul 2022 11:29:03 +0200 Subject: Setting up editors for the GNU/GCC coding style? In-Reply-To: <8735ekmkty.fsf@adacore.com> References: <8735ekmkty.fsf@adacore.com> Message-ID: <874jz09sio.fsf@euler.schwinge.homeip.net> Hi! On 2022-07-29T09:36:41+0200, Marc Poulhies via Gcc wrote: > Iannetta Paul writes: >> About configuring recent editors to follow the GNU coding style, I don't really >> know but it should always be possible to register a hook that will run `indent` >> when the file is saved. > > There is a clang-format config file in contrib that one can symlink in > the root dir as .clang-format. I hope/guess tools like CLion can pick it > and use it? At least this can be used to indent using clang-format tools > and derivatives (like git-clang-format). In the GCC Rust project, we are > using it (but judging by Jakub's last review for Philip's patch, the > config is maybe not exhaustive, or our setup is not correct). Simple answer there: these files are in 'gcc/config/' etc., but 'clang-format' is restricted to 'gcc/rust/' only (both in '.github/workflows/clang-format.yml' and 'CONTRIBUTING.md': "Running `clang-format` locally"). Unless everyone uses it, using 'clang-format' everywhere is too noisy; it has a very strict (in my opinion: restrictive) understanding of "proper" format. ;-) 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 From builder@sourceware.org Fri Jul 29 17:11:53 2022 From: builder@sourceware.org (builder@sourceware.org) Date: Fri, 29 Jul 2022 17:11:53 +0000 Subject: =?utf-8?q?=E2=98=BA_Buildbot_=28GNU_Toolchain=29=3A_gccrust_-_build_successful_=28master=29?= Message-ID: <20220729171153.A3A1B385780A@sourceware.org> A passing build has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/132/builds/70 Build state: build successful Revision: e88a55ab6919346e0afe79bfd13f84ecf9634889 Worker: bb1 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/132/builds/70/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/4/logs/stdio - warnings (28): https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/4/logs/warnings__28_ - 5: make check ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/5/logs/stdio - rust.sum: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/5/logs/rust_sum - rust.log: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/5/logs/rust_log - warnings (6): https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/5/logs/warnings__6_ - 6: grep unexpected rust.sum ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/6/logs/stdio - 7: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/7/logs/stdio - 8: build bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/8/logs/stdio - 9: fetch bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/9/logs/stdio - 10: unpack bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/10/logs/stdio - 11: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/11/logs/stdio - 12: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/12/logs/stdio - 13: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/13/logs/stdio - 14: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/14/logs/stdio - 15: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/15/logs/stdio - 16: make clean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/70/steps/16/logs/stdio