From: Mark Wielaard <firstname.lastname@example.org>
To: Tom de Vries <email@example.com>, firstname.lastname@example.org
Subject: Re: Fwd: Buildbot failure in Wildebeest Builder on whole buildset
Date: Thu, 25 Mar 2021 11:41:20 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On Thu, 2021-03-25 at 09:50 +0100, Tom de Vries wrote:
> I've just committed patch "Move hardlink handling out of dwz
> and there's this buildbot failure.
> Is there something easy that you can do to find out if this is a
> or not, f.i. retry the build for that bot?
I logged into the buildbot worker and did a dwz build myself.
make check does produce 32 unexpected failures.
Removing the last commit makes everything pass.
Adding the commit again produces the failures again.
It isn't a fluke.
The problem is simply that:
cp hello 1
Makes dwz produce an exit code of 1 which seems to be interpreted as
child process exited abnormally in a make check run.
running under valgrind --track-origins=yes gives:
==31313== Conditional jump or move depends on uninitialised value(s)
==31313== at 0x127974: dwz (dwz.c:15287)
==31313== by 0x10BB7C: dwz_with_low_mem (dwz.c:16227)
==31313== by 0x10BB7C: dwz_one_file (dwz.c:16253)
==31313== by 0x10BB7C: main (dwz.c:16532)
==31313== Uninitialised value was created by a stack allocation
==31313== at 0x10B59B: main (dwz.c:16513)
I haven't tracked down what res->res precisely depends on that doesn't
have a defined value.
next prev parent reply other threads:[~2021-03-25 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 8:41 buildbot
2021-03-25 8:50 ` Fwd: " Tom de Vries
2021-03-25 10:41 ` Mark Wielaard [this message]
2021-03-25 10:49 ` Mark Wielaard
2021-03-25 14:01 ` Tom de Vries
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).