From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Ross Burton <Ross.Burton@arm.com>
Subject: Re: [docs] [PATCH] release-notes-5.1: add beaglebone-yocto parselogs test oeqa failure
Date: Wed, 16 Oct 2024 15:36:28 +0200 [thread overview]
Message-ID: <b96c8eaf-df55-4276-8ec0-d7e8a7b60f42@cherry.de> (raw)
In-Reply-To: <20241016-5-1-parselogs-beagle-v1-1-ade903beb18a@bootlin.com>
Hi Antonin,
On 10/16/24 10:33 AM, Antonin Godard via lists.yoctoproject.org wrote:
> The beaglebone-yocto currently fails the parselogs runtime test. For
> details see: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15624
>
> Reported-by: Ross Burton <Ross.Burton@arm.com>
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
> documentation/migration-guides/release-notes-5.1.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/documentation/migration-guides/release-notes-5.1.rst b/documentation/migration-guides/release-notes-5.1.rst
> index 0f1cb5312e1a59fdfff2df57e98b6c4a27bd589d..7ce1ef2299189f7bdc566a8e549f4dea105626b5 100644
> --- a/documentation/migration-guides/release-notes-5.1.rst
> +++ b/documentation/migration-guides/release-notes-5.1.rst
> @@ -402,6 +402,12 @@ New Features / Enhancements in 5.1
> scripts, fixing some issues seen when :term:`PACKAGECONFIG` would
> conditionally modify it.
>
> +Known Issues in 5.1
> +~~~~~~~~~~~~~~~~~~~
> +
> +- ``oeqa/runtime``: the ``beaglebone-yocto`` target fails the ``parselogs``
> + runtime test due to unexpected kernel error messages in the log.
> +
We have a bugzilla entry, so please mention it so that people can follow
potential resolution without waiting on the docs to be updated (or us
forgetting to update it :) ).
I believe something like,
:yocto_bugs:`bug 15624 </show_bug.cgi?id=15624>`
should do the trick?
Interesting that there's a double whitespace after the dash, was that on
purpose? (Trying to figure out if we should mention this in the
standard.md or something :) )
Cheers,
Quentin
next prev parent reply other threads:[~2024-10-16 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 8:33 [PATCH] release-notes-5.1: add beaglebone-yocto parselogs test oeqa failure Antonin Godard
2024-10-16 13:36 ` Quentin Schulz [this message]
2024-10-16 14:15 ` [docs] " Antonin Godard
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=b96c8eaf-df55-4276-8ec0-d7e8a7b60f42@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=Ross.Burton@arm.com \
--cc=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=thomas.petazzoni@bootlin.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