All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yi Fan Yu" <yifan.yu@windriver.com>
To: Paul Eggleton <bluelightning@bluelightning.org>
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 12:34:26 -0400	[thread overview]
Message-ID: <6f253d24-f404-a901-83d0-bd10879c8a35@windriver.com> (raw)
In-Reply-To: <5446239.DvuYhMxLoT@linc>

On 3/28/21 10:23 PM, Paul Eggleton wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
> 
>   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.)
This is very strange, never seen this test appear in the failure list.
I looked at the more recent runs and don't see this failure reproduced.

Anyways I went ahead and made sure at least it works on my machine

```
on qemuarm64 running on my personal x86-64 machine

=== Test Summary ===
TOTAL: 408
PASSED: 390
FAILED: 0
SKIPPED: 18
DURATION: 2941
END: /usr/lib/valgrind/ptest


This is after the patch 1/2 3.16.1->3.17.0

TOTAL: 419
PASSED: 398
FAILED: 1
SKIPPED: 20
DURATION: 3053

Failed test is the drd/swapcontext

//yifan

      reply	other threads:[~2021-03-29 16:34 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   ` [oe-core][PATCH v3 1/2] valgrind: update 3.16.1 -> 3.17.0 Paul Eggleton
2021-03-29 16:34     ` Yi Fan Yu [this message]

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=6f253d24-f404-a901-83d0-bd10879c8a35@windriver.com \
    --to=yifan.yu@windriver.com \
    --cc=bluelightning@bluelightning.org \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.