Buildbot failure in Wildebeest Builder on whole buildset

Mark Wielaard mark@klomp.org
Wed Feb 26 21:59:00 GMT 2020


On Wed, Feb 26, 2020 at 09:42:26PM +0000, buildbot@builder.wildebeest.org wrote:
> The Buildbot has detected a failed build on builder whole buildset while building elfutils.
> Full details are available at:
>     https://builder.wildebeest.org/buildbot/#builders/16/builds/277
> 
> Buildbot URL: https://builder.wildebeest.org/buildbot/
> 
> Worker for this Build: centos-aarch64
> 
> Build Reason: <unknown>
> Blamelist: Konrad Kleine <kkleine@redhat.com>
> 
> BUILD FAILED: failed test (failure)

This is really strange. It doesn't seem to be related to the latest
commit. It seems to be some internal valgrind issue with the address
space manager:
https://builder.wildebeest.org/buildbot/#/builders/16/builds/277/steps/8/logs/test-suite_log

FAIL: run-nm-self.sh
====================
--18155:0: aspacem Valgrind: FATAL: aspacem assertion failed:
--18155:0: aspacem   sane_NSegment(&nsegments[i])
--18155:0: aspacem   at m_aspacemgr/aspacemgr-linux.c:728 (preen_nsegments)
--18155:0: aspacem Exiting now.

I'll try to replicate it and figure this out. But I think it doesn't
have to do anything with the elfutils code.

Cheers,

Mark



More information about the Elfutils-devel mailing list