All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Alexander Kanavin <alex@linutronix.de>,
	Ralph Siemsen <ralph.siemsen@linaro.org>,
	Li Wang <liwang@redhat.com>
Subject: Re: [PATCH 14/17] ltp: update 20210927 -> 20220121
Date: Thu, 27 Jan 2022 21:53:57 +0100	[thread overview]
Message-ID: <YfMGZYuARRuap8eW@pevik> (raw)
In-Reply-To: <CANNYZj9kn2hvwdZReHyE4SH9xm4gOAQ-7dtUEjoGJ-L8ixpJaQ@mail.gmail.com>

> On Thu, 27 Jan 2022 at 18:21, Petr Vorel <petr.vorel@gmail.com> wrote:

> > Hi Alexander,

> > > The ltp compliancy parser is rewritten to actually
> > > match the logs: they seem to be unstructured, test case names
> > > are not printed and the only indication of failure is appearance of
> > > FAIL[ED] somewhere.

> > I'd split meta/lib/oeqa/utils/logparser.py change into separate commit.
> > It's not related at all to the update.


> Without this, the update would break the ltp_compliancy ptest, as it would
> cause the parser to fail.
OK. If it can work with the previous version I'd commit it separately.
But maybe it's correct this way, I understand LTP, not openembedded.

Anyway, thanks for the update.

Kind regards,
Petr

> Alex


  reply	other threads:[~2022-01-27 20:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 10:19 [PATCH 01/17] mesa: fold mesa-gl variant into the main recipe using mcextend class Alexander Kanavin
2022-01-27 10:19 ` [PATCH 02/17] bind: upgrade 9.16.24 -> 9.16.25 Alexander Kanavin
2022-01-27 10:19 ` [PATCH 03/17] ifupdown: upgrade 0.8.36 -> 0.8.37 Alexander Kanavin
2022-01-27 10:19 ` [PATCH 04/17] ethtool: upgrade 5.15 -> 5.16 Alexander Kanavin
2022-01-27 10:19 ` [PATCH 05/17] webkitgtk: upgrade 2.34.3 -> 2.34.4 Alexander Kanavin
2022-01-27 10:19 ` [PATCH 06/17] debianutils: upgrade 5.5 -> 5.7 Alexander Kanavin
2022-01-27 10:19 ` [PATCH 07/17] diffoscope: upgrade 200 -> 201 Alexander Kanavin
2022-01-27 10:19 ` [PATCH 08/17] libbsd: upgrade 0.11.3 -> 0.11.5 Alexander Kanavin
2022-01-27 10:19 ` [PATCH 09/17] libical: upgrade 3.0.12 -> 3.0.13 Alexander Kanavin
2022-01-27 10:19 ` [PATCH 10/17] wpa-supplicant: update 2.9 -> 2.10 Alexander Kanavin
2022-01-27 10:19 ` [PATCH 11/17] zstd: update 1.5.0 -> 1.5.2 Alexander Kanavin
2022-01-27 18:56   ` [OE-core] " Khem Raj
2022-01-27 19:51     ` Alexander Kanavin
     [not found]     ` <16CE388D38E12D03.16917@lists.openembedded.org>
2022-01-27 20:09       ` Alexander Kanavin
2022-01-27 21:01         ` Khem Raj
2022-01-27 10:20 ` [PATCH 12/17] rust: update 1.58.0 -> 1.58.1 Alexander Kanavin
2022-01-27 10:20 ` [PATCH 13/17] gdb: update 11.1 -> 11.2 Alexander Kanavin
2022-01-27 18:12   ` [OE-core] " Khem Raj
2022-01-27 10:20 ` [PATCH 14/17] ltp: update 20210927 -> 20220121 Alexander Kanavin
2022-01-27 17:21   ` Petr Vorel
2022-01-27 19:25     ` Alexander Kanavin
2022-01-27 20:53       ` Petr Vorel [this message]
2022-01-27 10:20 ` [PATCH 15/17] gnutls: update 3.7.2 -> 3.7.3 Alexander Kanavin
2022-01-27 10:20 ` [PATCH 16/17] libusb1: correct SRC_URI Alexander Kanavin
2022-01-27 10:20 ` [PATCH 17/17] gobject-introspection: replace prelink-rtld with objdump -p Alexander Kanavin
2022-01-27 18:09   ` [OE-core] " Khem Raj
2022-01-27 19:26     ` Alexander Kanavin

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=YfMGZYuARRuap8eW@pevik \
    --to=petr.vorel@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=liwang@redhat.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ralph.siemsen@linaro.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.