From: Adrian Bunk <bunk@stusta.de>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [v2 4/4] valgrind: disable 256 ptests for aarch64
Date: Wed, 11 Sep 2019 17:00:16 +0300 [thread overview]
Message-ID: <20190911140016.GB27961@localhost> (raw)
In-Reply-To: <f87d660d-9c05-dfdd-ced2-88cfc9a38a4f@windriver.com>
On Wed, Sep 11, 2019 at 09:38:53AM -0400, Randy MacLeod wrote:
> On 9/11/19 8:32 AM, Adrian Bunk wrote:
> > On Tue, Sep 10, 2019 at 05:41:36PM -0400, Randy MacLeod wrote:
> > > On qemuarm64 systems, about half of the valgrind tests fail and
> > > often result in defunct processes, eg:
> > > root 819 818 25 00:12 pts/0 00:01:52 /usr/bin/valgrind --command-line-only=yes --memcheck:leak-check=no --tool=memcheck -q --track-origins=
> > > root 861 420 0 00:13 pts/0 00:00:00 [sh] <defunct>
> > > Eventually these processes use so much memory that the
> > > out of memory killer runs.
> > >
> > > Hide the tests that fail as a horrid work-around until the
> > > root cause has been resolved since this at least allows the
> > > ptest run to complete.
> > > ...
> >
> > I can reproduce this on hardware,
>
> Ah good, I was wondering if it was just happening on qemu.
>
> > and I have the bad feeling that no one
> > will work on resolving the root cause if this is work-arounded in ptest.
> >
> > IMHO this should instead be listed as M3 blocker,
> > similar to "strace ptest timeout".
>
> Well, I've enabled 100s of tests that were not being run before
> and most of them pass for qemux86-64 so I don't think it
> should be an M3 blocker like strace since it isn't a regression.
I just tried to reproduce in warrior and it did,
so it doesn't seem to be a regression.
> I did start to debug valgrind but it's a bit of a complicated
> program and will take time so this work-around makes sense to
> me. If no one else gets to it before me, I'll come back to
> debugging this issue but likely not before early 3.1.
It would be good if you could also open a bug, so that people can see
that there is a problem with this package on an important architecture.
> Thanks,
> ../Randy
Thanks
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-09-11 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 21:41 [v2 1/4] valgrind: enable ~500 more ptests Randy MacLeod
2019-09-10 21:41 ` [v2 2/4] valgrind: make a few more ptests pass Randy MacLeod
2019-09-10 21:41 ` [v2 3/4] valgrind: ptest improvements to run-ptest and more Randy MacLeod
2019-09-10 21:41 ` [v2 4/4] valgrind: disable 256 ptests for aarch64 Randy MacLeod
2019-09-11 12:32 ` Adrian Bunk
2019-09-11 13:38 ` Randy MacLeod
2019-09-11 14:00 ` Adrian Bunk [this message]
2019-09-11 18:01 ` Randy MacLeod
2019-09-12 8:13 ` Adrian Bunk
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=20190911140016.GB27961@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
/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