From: "Paul Eggleton" <bluelightning@bluelightning.org>
To: Yi Fan Yu <yifan.yu@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH v3 1/2] valgrind: update 3.16.1 -> 3.17.0
Date: Mon, 29 Mar 2021 15:23:47 +1300 [thread overview]
Message-ID: <5446239.DvuYhMxLoT@linc> (raw)
In-Reply-To: <20210326143710.168053-1-yifan.yu@windriver.com>
Hi Yi Fan
On Saturday, 27 March 2021 03:37:09 NZDT Yi Fan Yu wrote:
> Notable changes:
> * library is now in libexecdir instead of libdir
>
> Added patches:
> * Add musl.supp: missing musl.supp in 3.17.0
>
> Dropped backport patches:
> * nlcontrolc: found in c79180a3afcf65902e578646c3b716cc749db406
> * drd Fedora33: found in 15330adf7c2471fbaa6a0818db07078d81dbff97
> * lmw lswi ppc64le: found in 74b74174d572fee4015b8f4e326db3cd949bcdc3
>
> Other dropped patches
> * helgrind intercept: found in d2d54dbcc74244adfc0c80b40862edf2b82f53b9
> * drd musl fix: found in d2d54dbcc74244adfc0c80b40862edf2b82f53b9
>
> TESTING RESULTS:
> qemux86-64:
> FAIL: drd/tests/swapcontext
>
> 3.17.0 3.16.1
> ===================
> TOTAL: 736 726
> PASSED: 694 688
> FAILED: 1 0
> SKIPPED: 41 38
Can you take a look at the following ptest failure:
AssertionError: Failed ptests:
{'valgrind': ['callgrind/tests/simwork-branch']}
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1657/steps/12/logs/stdio
(To be fair I'm not 100% sure if this only started happening after your patch though.)
Thanks
Paul
next prev parent reply other threads:[~2021-03-29 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166FB59AC0FDC39E.19792@lists.openembedded.org>
2021-03-26 14:37 ` [oe-core][PATCH v3 1/2] valgrind: update 3.16.1 -> 3.17.0 Yi Fan Yu
2021-03-26 14:37 ` [oe-core][PATCH v3 2/2] valgrind: Disable ptest swapcontext.vgtest Yi Fan Yu
2021-03-29 2:23 ` Paul Eggleton [this message]
2021-03-29 16:34 ` [oe-core][PATCH v3 1/2] valgrind: update 3.16.1 -> 3.17.0 Yi Fan Yu
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=5446239.DvuYhMxLoT@linc \
--to=bluelightning@bluelightning.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=yifan.yu@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