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: Tue, 04 Jun 2024 12:56:40 +0100	[thread overview]
Message-ID: <57260bcac841a038fc1e0af5dad1d66f28dd111c.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAHUKmYa1kyhrJQ8C3o9zyx15FvjzxdBs5D=4GUU-33T7v53NSA@mail.gmail.com>

On Tue, 2024-06-04 at 13:45 +0200, Etienne Cordonnier wrote:
> Thanks Richard, this is helpful.
> This shows that test_systemd_coredump_minidebuginfo is skipped / not
> executed, so I'm quite sure the test is still failing in CI as you
> had reported in December. I've sent a patch to fix what I think is
> causing the CI issue, and another patch to enable the feature in
> poky-altcfg once the CI failure is fixed.

I think it is being tested. There is this test:

https://git.yoctoproject.org/poky/tree/meta/lib/oeqa/selftest/cases/minidebuginfo.py

which is run with oe-selftest -r minidebuginfo

which generates results here:


https://git.yoctoproject.org/yocto-testresults/tree/oeselftest/testresults.json

e.g.:

            "minidebuginfo.Minidebuginfo.test_minidebuginfo": {
                "duration": 1073.8962650299072,
                "status": "PASSED"
            },

            "minidebuginfo.Minidebuginfo.test_minidebuginfo": {
                "duration": 764.4718866348267,
                "status": "PASSED"
            },

so I think it is being tested in each oe-selftest run (hence the
multiple results)?

Cheers,

Richard



  reply	other threads:[~2024-06-04 11:56 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
     [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 [this message]
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=57260bcac841a038fc1e0af5dad1d66f28dd111c.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