Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Etienne Cordonnier <ecordonnier@snap.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] oeqa/runtime: fix regression in minidebuginfo test
Date: Mon, 03 Jun 2024 15:13:35 +0100	[thread overview]
Message-ID: <8efc26ec3c4a81ab92b3108707eecb0250d5b7bd.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAHUKmYY53BOSRdFvxwsTeDOXfurLbvJ9yS6by-K4mR1OshvFRg@mail.gmail.com>

On Mon, 2024-06-03 at 13:35 +0200, Etienne Cordonnier wrote:
> Hi Richard,
> thanks for merging the v2 of this patch. Is this test running in CI
> currently? I'm thinking I could send a PR to enable minidebuginfo in
> poky-altcfg, but is there a way I can verify that this test works in
> yocto's CI? (it works locally, but as I mentioned it would fail on a
> kernel with CONFIG_USER_NS disabled.)

I'd have expected it to be tested in CI, yes.

You can see results here for example:

https://git.yoctoproject.org/yocto-testresults/tree/runtime/poky-altcfg/qemux86-64/core-image-sato-sdk/testresults.json

Cheers,

Richard


  parent reply	other threads:[~2024-06-03 14:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 10:08 [PATCH] oeqa/runtime: fix regression in minidebuginfo test ecordonnier
2024-05-29 14:54 ` [OE-core] " Richard Purdie
2024-05-30 15:23   ` Etienne Cordonnier
     [not found]   ` <17D44D900E0F42D1.15404@lists.openembedded.org>
2024-06-03 11:35     ` Etienne Cordonnier
2024-06-03 11:42       ` Alexander Kanavin
2024-06-03 14:13       ` Richard Purdie [this message]
     [not found]       ` <17D5840BB429ED6B.21428@lists.openembedded.org>
2024-06-03 14:28         ` Richard Purdie
2024-06-04 11:45           ` Etienne Cordonnier
2024-06-04 11:56             ` Richard Purdie
2024-06-04 11:58               ` Etienne Cordonnier
2024-06-04 12:32                 ` Richard Purdie
2024-06-05 10:11                   ` Etienne Cordonnier

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=8efc26ec3c4a81ab92b3108707eecb0250d5b7bd.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=ecordonnier@snap.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox