From: "Alex Bennée" <alex.bennee@linaro.org>
To: Cornelia Huck <cohuck@redhat.com>
Cc: "Aleksandar Markovic" <aleksandar.qemu.devel@gmail.com>,
"Alex Bennée" <1883560@bugs.launchpad.net>,
"Laurent Vivier" <laurent@vivier.eu>,
qemu-devel@nongnu.org
Subject: Re: [Bug 1883560] [NEW] mips linux-user builds occasionly crash randomly only to be fixed by a full clean re-build
Date: Fri, 19 Jun 2020 09:21:55 +0100 [thread overview]
Message-ID: <87h7v7v524.fsf@linaro.org> (raw)
In-Reply-To: <20200619081723.10594336.cohuck@redhat.com>
Cornelia Huck <cohuck@redhat.com> writes:
> On Thu, 18 Jun 2020 19:00:34 +0200
> Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> wrote:
>
>> четвртак, 18. јун 2020., Cornelia Huck <cohuck@redhat.com> је написао/ла:
>>
>> > On Mon, 15 Jun 2020 15:18:48 -0000
>> > Alex Bennée <1883560@bugs.launchpad.net> wrote:
>> >
>> > > Public bug reported:
>> > >
>> > > >From time to time I find check-tcg crashes with a one of the MIPS
>> > > binaries. The last time it crashed was running the test:
>> > >
>> > > ./mips64el-linux-user/qemu-mips64el ./tests/tcg/mips64el-linux-
>> > > user/threadcount
>> > >
>> > > Inevitably after some time noodling around wondering what could be
>> > > causing this weird behaviour I wonder if it is a build issue. I wipe all
>> > > the mips* build directories, re-run configure and re-build and voila
>> > > problem goes away.
>> > >
>> > > It seems there must be some sort of build artefact which isn't being
>> > > properly re-generated on a build update which causes weird problems.
>> > > Additional data point if I:
>> > >
>> > > rm -rf mips64el-linux-user
>> > > ../../configure
>> > > make
>> > >
>> > > then I see failures in mip32 builds - eg:
>> > >
>> > > GEN mipsn32el-linux-user/config-target.h
>> > > In file included from /home/alex/lsrc/qemu.git/
>> > linux-user/syscall_defs.h:10,
>> > > from /home/alex/lsrc/qemu.git/linux-user/qemu.h:16,
>> > > from /home/alex/lsrc/qemu.git/
>> > linux-user/linuxload.c:5:
>> > > /home/alex/lsrc/qemu.git/linux-user/mips64/syscall_nr.h:1: error:
>> > unterminated #ifndef
>> > > #ifndef LINUX_USER_MIPS64_SYSCALL_NR_H
>> > >
>> > > make[1]: *** [/home/alex/lsrc/qemu.git/rules.mak:69:
>> > linux-user/linuxload.o] Error 1
>> > > make[1]: *** Waiting for unfinished jobs....
>> > >
>> > > which implies there is a cross dependency between different targets
>> > > somewhere. If I executed:
>> > >
>> > > rm -rf mips*
>> > >
>> > > before re-configuring and re-building then everything works again.
>> > >
>> > > ** Affects: qemu
>> > > Importance: Undecided
>> > > Status: New
>> > >
>> > >
>> > > ** Tags: build linux-user mips
>> > >
>> >
>> > FWIW, this does not seem to be a mips-only issue: I'm seeing the
>> > threadcount test fail with s390x-linux-user as well, and it also goes
>> > away (only) if I purge the build directory, re-configure, and re-build.
>> >
>> >
>> >
>> Alex, Cornelia,
>>
>> Do you perhaps recall how did you obtain the original binaries (those with
>> the problem)? What would be your typical workflow? Perhaps "git-pull +
>> make" on existing, but not latest source tree?
>
> Just a bog-standard "pull some stuff, do make, create a branch and put
> some patches on it, do make, switch to another branch, do make, etc". No
> advanced fiddling with git history, doing make on a subtree, etc.
Same here. As I say the syscall_nr breakage was a different one. I'll
regularly just advance my tree and find this sort of breakage.
--
Alex Bennée
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <1883560@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1883560] [NEW] mips linux-user builds occasionly crash randomly only to be fixed by a full clean re-build
Date: Fri, 19 Jun 2020 08:21:55 -0000 [thread overview]
Message-ID: <87h7v7v524.fsf@linaro.org> (raw)
Message-ID: <20200619082155.UPW4P8vdXkr1WMtJSXeGr5Ul8zy6tJOMl__FwGSg-fg@z> (raw)
In-Reply-To: 159223432851.7281.13140123017230519248.malonedeb@gac.canonical.com
Cornelia Huck <cohuck@redhat.com> writes:
> On Thu, 18 Jun 2020 19:00:34 +0200
> Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> wrote:
>
>> четвртак, 18. јун 2020., Cornelia Huck <cohuck@redhat.com> је написао/ла:
>>
>> > On Mon, 15 Jun 2020 15:18:48 -0000
>> > Alex Bennée <1883560@bugs.launchpad.net> wrote:
>> >
>> > > Public bug reported:
>> > >
>> > > >From time to time I find check-tcg crashes with a one of the MIPS
>> > > binaries. The last time it crashed was running the test:
>> > >
>> > > ./mips64el-linux-user/qemu-mips64el ./tests/tcg/mips64el-linux-
>> > > user/threadcount
>> > >
>> > > Inevitably after some time noodling around wondering what could be
>> > > causing this weird behaviour I wonder if it is a build issue. I wipe all
>> > > the mips* build directories, re-run configure and re-build and voila
>> > > problem goes away.
>> > >
>> > > It seems there must be some sort of build artefact which isn't being
>> > > properly re-generated on a build update which causes weird problems.
>> > > Additional data point if I:
>> > >
>> > > rm -rf mips64el-linux-user
>> > > ../../configure
>> > > make
>> > >
>> > > then I see failures in mip32 builds - eg:
>> > >
>> > > GEN mipsn32el-linux-user/config-target.h
>> > > In file included from /home/alex/lsrc/qemu.git/
>> > linux-user/syscall_defs.h:10,
>> > > from /home/alex/lsrc/qemu.git/linux-user/qemu.h:16,
>> > > from /home/alex/lsrc/qemu.git/
>> > linux-user/linuxload.c:5:
>> > > /home/alex/lsrc/qemu.git/linux-user/mips64/syscall_nr.h:1: error:
>> > unterminated #ifndef
>> > > #ifndef LINUX_USER_MIPS64_SYSCALL_NR_H
>> > >
>> > > make[1]: *** [/home/alex/lsrc/qemu.git/rules.mak:69:
>> > linux-user/linuxload.o] Error 1
>> > > make[1]: *** Waiting for unfinished jobs....
>> > >
>> > > which implies there is a cross dependency between different targets
>> > > somewhere. If I executed:
>> > >
>> > > rm -rf mips*
>> > >
>> > > before re-configuring and re-building then everything works again.
>> > >
>> > > ** Affects: qemu
>> > > Importance: Undecided
>> > > Status: New
>> > >
>> > >
>> > > ** Tags: build linux-user mips
>> > >
>> >
>> > FWIW, this does not seem to be a mips-only issue: I'm seeing the
>> > threadcount test fail with s390x-linux-user as well, and it also goes
>> > away (only) if I purge the build directory, re-configure, and re-build.
>> >
>> >
>> >
>> Alex, Cornelia,
>>
>> Do you perhaps recall how did you obtain the original binaries (those with
>> the problem)? What would be your typical workflow? Perhaps "git-pull +
>> make" on existing, but not latest source tree?
>
> Just a bog-standard "pull some stuff, do make, create a branch and put
> some patches on it, do make, switch to another branch, do make, etc". No
> advanced fiddling with git history, doing make on a subtree, etc.
Same here. As I say the syscall_nr breakage was a different one. I'll
regularly just advance my tree and find this sort of breakage.
--
Alex Bennée
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1883560
Title:
mips linux-user builds occasionly crash randomly only to be fixed by a
full clean re-build
Status in QEMU:
New
Bug description:
From time to time I find check-tcg crashes with a one of the MIPS
binaries. The last time it crashed was running the test:
./mips64el-linux-user/qemu-mips64el ./tests/tcg/mips64el-linux-
user/threadcount
Inevitably after some time noodling around wondering what could be
causing this weird behaviour I wonder if it is a build issue. I wipe
all the mips* build directories, re-run configure and re-build and
voila problem goes away.
It seems there must be some sort of build artefact which isn't being
properly re-generated on a build update which causes weird problems.
Additional data point if I:
rm -rf mips64el-linux-user
../../configure
make
then I see failures in mip32 builds - eg:
GEN mipsn32el-linux-user/config-target.h
In file included from /home/alex/lsrc/qemu.git/linux-user/syscall_defs.h:10,
from /home/alex/lsrc/qemu.git/linux-user/qemu.h:16,
from /home/alex/lsrc/qemu.git/linux-user/linuxload.c:5:
/home/alex/lsrc/qemu.git/linux-user/mips64/syscall_nr.h:1: error: unterminated #ifndef
#ifndef LINUX_USER_MIPS64_SYSCALL_NR_H
make[1]: *** [/home/alex/lsrc/qemu.git/rules.mak:69: linux-user/linuxload.o] Error 1
make[1]: *** Waiting for unfinished jobs....
which implies there is a cross dependency between different targets
somewhere. If I executed:
rm -rf mips*
before re-configuring and re-building then everything works again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1883560/+subscriptions
next prev parent reply other threads:[~2020-06-19 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 15:18 [Bug 1883560] [NEW] mips linux-user builds occasionly crash randomly only to be fixed by a full clean re-build Alex Bennée
2020-06-15 16:57 ` [Bug 1883560] " Laurent Vivier
2020-06-16 16:49 ` Alex Bennée
2020-06-18 11:53 ` [Bug 1883560] [NEW] " Cornelia Huck
2020-06-18 15:11 ` Aleksandar Markovic
2020-06-18 15:11 ` Aleksandar Markovic
2020-06-18 17:00 ` Aleksandar Markovic
2020-06-18 17:00 ` Aleksandar Markovic
2020-06-19 6:17 ` Cornelia Huck
2020-06-19 8:21 ` Alex Bennée [this message]
2020-06-19 8:21 ` Alex Bennée
2020-06-18 17:34 ` [Bug 1883560] " Laurent Vivier
2021-04-29 10:26 ` Thomas Huth
2021-06-29 4:17 ` Launchpad Bug Tracker
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7v7v524.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=1883560@bugs.launchpad.net \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=cohuck@redhat.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 NNTP newsgroup(s).