[Bug debuginfod/30879] intermittent failure (libstdc++ uncaught exception terminate) during testsuite on sparc-gentoo
https://sourceware.org/bugzilla/show_bug.cgi?id=30879 Frank Ch. Eigler changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Frank Ch. Eigler --- Author: Frank Ch. Eigler Date: Fri Sep 22 15:30:51 2023 -0400 PR30879: intermittent debuginfod crash with unhandled exception -- You are receiving this mail because: You are on the CC list for the bug.
Re: [PATCH 01/14] libdw: Make try_split_file static
Hi Omar, On Wed, 2023-09-27 at 11:20 -0700, Omar Sandoval wrote: > It's only used in libdw_find_split_unit.c. Obvious correct. Applied. Thanks, Mark
Re: [PATCH 02/14] libdw: Handle split DWARF in dwarf_entrypc
Hi Omar, On Wed, 2023-09-27 at 11:20 -0700, Omar Sandoval wrote: > From: Omar Sandoval > > If a DIE has no DW_AT_entry_pc attribute, dwarf_entrypc looks for > DW_AT_low_pc in that DIE. But for a split compilation unit DIE, > DW_AT_low_pc is in the corresponding skeleton DIE, so this fails. > dwarf_lowpc already handles this fallback, so use it instead. Nice find. Also interesting varlocs already "tested" for that and we hadn't noticed before. Applied. Thanks, Mark
Re: [PATCH 03/14] libdw: Handle DW_AT_ranges in split DWARF 5 skeleton in dwarf_ranges
Hi Omar,
On Wed, 2023-09-27 at 11:20 -0700, Omar Sandoval wrote:
> From: Omar Sandoval
>
> When commit 879f3a4f99df ("libdw: Handle .debug_rnglists in
> dwarf_ranges.") added support for split DWARF 5 in 2018, GCC put all
> range lists for split DWARF in the .debug_rnglists section of the
> skeleton file (similarly to GNU DebugFission, which puts all range lists
> in .debug_ranges in the skeleton file).
>
> In 2021, after a discussion on the dwarf-discuss mailing list [1], GCC
> changed this to match Clang's behavior. Now, ranges are in
> .debug_rnglists.dwo in the split file, _except_ for one: the skeleton
> unit DIE has a DW_AT_ranges attribute, and its ranges are in
> .debug_rnglists in the skeleton file. See GCC commit 4b33c5aaab9e
> ("dwarf2out: Fix up ranges for -gdwarf-5 -gsplit-dwarf [PR99490]") and
> the Issue 210310.1 clarifying the DWARF standard [2].
>
> Unfortunately, this confuses dwarf_ranges, which always uses
> .debug_rnglists.dwo if it exists. Fix it by special casing the unit
> DIE: its range lists should be in .debug_rnglists if that exists, and
> .debug_rnglists.dwo otherwise.
>
> 1: https://lists.dwarfstd.org/pipermail/dwarf-discuss/2021-March/002009.html
> 2: https://dwarfstd.org/issues/210310.1.html
Thanks for all these references in the commit message.
With that the 2 line change looks good. Applied.
Thanks,
Mark
Re: [PATCH 04/14] libdw: Handle other string forms in dwarf_macro_param2
Hi Omar, On Wed, 2023-09-27 at 11:20 -0700, Omar Sandoval wrote: > From: Omar Sandoval > > dwarf_getmacros handles the additional macro string forms added by DWARF > 5, but dwarf_macro_param2 doesn't. Update it with the list of all > string forms allowed in .debug_macro. In particular, GCC and Clang > generate DW_MACRO_define_strx and DW_MACRO_undef_strx, which > dwarf_macro_param2 couldn't handle. So as far as I can see this is always only used for DWARF5 forms and never uses the DW_FORM_GNU_strp_alt or DW_FORM_GNU_str_index because the GNU DebugFission extension for DWARF4 kept the old macinfo format, just moved it to the dwo. Thanks for catching this. Applied. Cheers, Mark
☠ Buildbot (Sourceware): elfutils - failed test (failure) (master)
A new failure has been detected on builder elfutils-centos-x86_64 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/39/builds/223 Build state: failed test (failure) Revision: 5b065f8583b00afbd3276c04b1b1d8fdf7d8a298 Worker: centos-x86_64 Build Reason: (unknown) Blamelist: Omar Sandoval Steps: - 0: worker_preparation ( success ) - 1: set package name ( success ) - 2: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/2/logs/stdio - 3: autoreconf ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/3/logs/stdio - 4: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/4/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/4/logs/config_log - 5: get version ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/5/logs/stdio - property changes: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/5/logs/property_changes - 6: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/6/logs/stdio - warnings (2): https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/6/logs/warnings__2_ - 7: make check ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/7/logs/stdio - test-suite.log: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/7/logs/test-suite_log - 8: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/8/logs/stdio - 9: build bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/9/logs/stdio - 10: fetch bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/10/logs/stdio - 11: unpack bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/11/logs/stdio - 12: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/12/logs/stdio - 13: pass .bunsen.source.gitdescribe ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/13/logs/stdio - 14: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/14/logs/stdio - 15: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/15/logs/stdio - 16: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/16/logs/stdio - 17: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/17/logs/stdio - 18: make distclean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/223/steps/18/logs/stdio
☺ Buildbot (Sourceware): elfutils - build successful (master)
A restored build has been detected on builder elfutils-centos-x86_64 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/39/builds/224 Build state: build successful Revision: 626186d6e7595121fd34234a574e9cecbea99a1a Worker: centos-x86_64 Build Reason: (unknown) Blamelist: Omar Sandoval Steps: - 0: worker_preparation ( success ) - 1: set package name ( success ) - 2: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/2/logs/stdio - 3: autoreconf ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/3/logs/stdio - 4: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/4/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/4/logs/config_log - 5: get version ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/5/logs/stdio - property changes: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/5/logs/property_changes - 6: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/6/logs/stdio - warnings (2): https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/6/logs/warnings__2_ - 7: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/7/logs/stdio - test-suite.log: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/7/logs/test-suite_log - 8: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/8/logs/stdio - 9: build bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/9/logs/stdio - 10: fetch bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/10/logs/stdio - 11: unpack bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/11/logs/stdio - 12: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/12/logs/stdio - 13: pass .bunsen.source.gitdescribe ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/13/logs/stdio - 14: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/14/logs/stdio - 15: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/15/logs/stdio - 16: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/16/logs/stdio - 17: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/17/logs/stdio - 18: make distclean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/224/steps/18/logs/stdio
☠ Buildbot (Sourceware): elfutils - failed test (failure) (master)
A new failure has been detected on builder elfutils-gentoo-sparc while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/225/builds/97 Build state: failed test (failure) Revision: c9c9ffae725009b192b40e2d89035f353ae7055f Worker: gentoo-sparc Build Reason: (unknown) Blamelist: Omar Sandoval Steps: - 0: worker_preparation ( success ) - 1: set package name ( success ) - 2: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/2/logs/stdio - 3: autoreconf ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/3/logs/stdio - 4: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/4/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/4/logs/config_log - 5: get version ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/5/logs/stdio - property changes: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/5/logs/property_changes - 6: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/6/logs/stdio - warnings (3): https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/6/logs/warnings__3_ - 7: make check ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/7/logs/stdio - test-suite.log: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/7/logs/test-suite_log - 8: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/8/logs/stdio - 9: build bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/9/logs/stdio - 10: fetch bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/10/logs/stdio - 11: unpack bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/11/logs/stdio - 12: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/12/logs/stdio - 13: pass .bunsen.source.gitdescribe ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/13/logs/stdio - 14: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/14/logs/stdio - 15: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/15/logs/stdio - 16: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/16/logs/stdio - 17: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/17/logs/stdio - 18: make distclean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/97/steps/18/logs/stdio
☝ Buildbot (Sourceware): elfutils - cancelled (master)
A cancelled build has been detected on builder elfutils-gentoo-sparc while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/225/builds/100 Build state: cancelled Revision: c9c9ffae725009b192b40e2d89035f353ae7055f Worker: gentoo-sparc Build Reason: (unknown) Blamelist: Omar Sandoval Steps: - 0: worker_preparation ( success ) - 1: set package name ( success ) - 2: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/100/steps/2/logs/stdio
☺ Buildbot (Sourceware): elfutils - build successful (master)
A restored build has been detected on builder elfutils-gentoo-sparc while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/225/builds/98 Build state: build successful Revision: 8a0d1d7ee7371c086fc11c166160196515c210e6 Worker: gentoo-sparc Build Reason: (unknown) Blamelist: Omar Sandoval Steps: - 0: worker_preparation ( success ) - 1: set package name ( success ) - 2: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/2/logs/stdio - 3: autoreconf ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/3/logs/stdio - 4: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/4/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/4/logs/config_log - 5: get version ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/5/logs/stdio - property changes: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/5/logs/property_changes - 6: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/6/logs/stdio - warnings (3): https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/6/logs/warnings__3_ - 7: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/7/logs/stdio - test-suite.log: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/7/logs/test-suite_log - 8: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/8/logs/stdio - 9: build bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/9/logs/stdio - 10: fetch bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/10/logs/stdio - 11: unpack bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/11/logs/stdio - 12: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/12/logs/stdio - 13: pass .bunsen.source.gitdescribe ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/13/logs/stdio - 14: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/14/logs/stdio - 15: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/15/logs/stdio - 16: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/16/logs/stdio - 17: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/17/logs/stdio - 18: make distclean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/98/steps/18/logs/stdio
Re: [PATCH 05/14] libdw: Fix dwarf_macro_getsrcfiles for DWARF 5
Hi Omar, On Wed, Sep 27, 2023 at 11:20:54AM -0700, Omar Sandoval wrote: > Dwarf_Macro_Op_Table::is_64bit conflates the address size and the offset > size: for .debug_macinfo, it is initialized based on the compilation > unit's address size, but for .debug_macro, it is initialized based on > the macro unit's offset size. is_64bit is used to determine the address > size to pass to __libdw_getsrclines. For a 64-bit architecture using > DWARF 5 with 32-bit offsets (the common case), this fails because > read_srclines checks that the given address size matches the address > size from the line number program header. > > Fix it by splitting is_64bit into separate address_size and offset_size > members. Very nice catch. You are right that for DWARF5 the line table header already gives the address_size. It is slightly embarassing our sanity check here failed. Thanks for fixing. I had to think a bit on why we didn't need to set the address_size for the fake_cu. But that is only needed to read address class forms. Which aren't valid forms in macro data. Applied, Mark
Re: [PATCH 06/14] libdw: Handle split DWARF in dwarf_macro_getsrcfiles
Hi Omar, On Wed, Sep 27, 2023 at 11:20:55AM -0700, Omar Sandoval wrote: > Macro information references file names from the line number information > table, which is tricky in split DWARF for a couple of reasons. > > First, the line number information for a macro unit comes from the > .debug_line.dwo section in the split file, not the .debug_line section > in the skeleton file. This was not specified in the GNU DebugFission > design document [1] or the DWARF 5 standard, but it is how GCC and Clang > behave in practice and was clarified in DWARF standard issue > 200602.1 [2] for the upcoming DWARF 6 standard. > > dwarf_macro_getsrcfiles uses the line number information from whichever > Dwarf handle it was passed. This is error-prone, since the most natural > thing to do is to pass the skeleton Dwarf handle. Fix this by storing > the appropriate Dwarf handle in Dwarf_Macro_Op_Table and using that one. Too bad we cannot fix the function signature because that would be an API break. But this makes sense (thanks again for the references). > Second, for .debug_macinfo.dwo in GNU DebugFission (generated by gcc > -gdwarf-4 -gstrict-dwarf -gsplit-dwarf), the offset into .debug_line.dwo > is implicitly 0. Again, this isn't in any specification, but it's how > GCC behaves in practice (Clang never generates macro information for > DWARF 4 split DWARF). Make get_macinfo_table default to 0 for split > DWARF when it can't find DW_AT_stmt_list. Makes sense, it cannot really be any other offset than zero. Applied, Mark
Re: [PATCH 00/14] elfutils: DWARF package (.dwp) file support
Hi Omar, On Wed, Sep 27, 2023 at 11:20:49AM -0700, Omar Sandoval wrote: > This patch series adds support for DWARF package files to libdw and the > elfutils tools. It supports the GNU DebugFission format for DWARF 4 [1] > and the format standardized in DWARF 5 (section 7.3.5 "DWARF Package > Files"). It supports both automatically opening the .dwp file for a > skeleton unit and examining the .dwp file alone, just like for .dwo > files. > > Patch 1 is a trivial cleanup I found while developing this. Patches 2-6 > are fixes for unrelated bugs in split DWARF and/or DWARF 5 that I > encountered while adding test cases for this series. I didn't add test > cases explicitly for those fixes because they are covered by the dwp > tests later in the series. > > The actual dwp support is in patches 7-10 and 13, including test cases. > Patches 11 and 12 enable testing macro information in dwp files. Patch > 14 adds support and tests for an LLVM extension to the dwp format. Thanks, I went through patches 1 to 6 and applied them all. Sorry for the buildbot failures, neither the centos7 x86_64 one, nor the gentoo sparc one is obviously caused by your patches. And both were spurious, later builds are green again. I'll go through the rest later. But there are more unreviewed patches, so it might take a bit. Thanks, Mark
☺ Buildbot (Sourceware): elfutils - build successful (master)
A restored build has been detected on builder elfutils-gentoo-sparc while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/225/builds/101 Build state: build successful Revision: 4bddabc1e7f3020b83a5abd98901146c58da403e Worker: gentoo-sparc Build Reason: (unknown) Blamelist: Omar Sandoval Steps: - 0: worker_preparation ( success ) - 1: set package name ( success ) - 2: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/2/logs/stdio - 3: autoreconf ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/3/logs/stdio - 4: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/4/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/4/logs/config_log - 5: get version ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/5/logs/stdio - property changes: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/5/logs/property_changes - 6: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/6/logs/stdio - warnings (3): https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/6/logs/warnings__3_ - 7: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/7/logs/stdio - test-suite.log: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/7/logs/test-suite_log - 8: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/8/logs/stdio - 9: build bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/9/logs/stdio - 10: fetch bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/10/logs/stdio - 11: unpack bunsen.cpio.gz ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/11/logs/stdio - 12: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/12/logs/stdio - 13: pass .bunsen.source.gitdescribe ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/13/logs/stdio - 14: pass .bunsen.source.gitbranch ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/14/logs/stdio - 15: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/15/logs/stdio - 16: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/16/logs/stdio - 17: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/17/logs/stdio - 18: make distclean ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/101/steps/18/logs/stdio
