release-notes-5.1: add beaglebone-yocto parselogs test oeqa failure

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(+)


---
base-commit: 3820a7bec0bb23bcd26bd99be2275d6d214a3a04
change-id: 20241016-5-1-parselogs-beagle-629a0ed73704

Best regards,

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

Hi Quentin,

On Wed Oct 16, 2024 at 3:36 PM CEST, Quentin Schulz wrote:
> 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?

Great suggestion, I didn't know - thanks!

> 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 :) )

Yes, it's part of the standards file actually:

  Though not strictly required by Sphinx, we have also chosen
  to use two space characters after ``-`` to introduce each
  list item

Surprising to me as well and makes my editor act weirdly, but the entire docs
were written that way heh.

Cheers,
Antonin

--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com