From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 05/17] unfs: update 0.9.22 -> 0.10.0
Date: Tue, 22 Nov 2022 15:09:21 +0000 [thread overview]
Message-ID: <ab2f02ff2654669a3c0b26bf741514698966b292.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-HbuCeOiK2yd_01ruShEg17J6yAKH2F4QTEp6hi9O+Pg@mail.gmail.com>
On Tue, 2022-11-22 at 16:03 +0100, Alexander Kanavin wrote:
> On Tue, 22 Nov 2022 at 13:29, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > I understand why you want to do that but this will totally break the
> > nfs export support, I could see at least one issue having looked at the
> > first few patches this was dropping.
>
> I can go over every spot in poky/ where unfs is mentioned and verify
> that it works correctly there, would that be ok?
It would help, yes. If you do that it could be good to understand and
document which areas we do/don't have test coverage of some kind for as
we could then look at either adding it or dropping that support if it
isn't used.
>
> There was one failure in a-full with glibc tests, and that's fixed,
> but I can see there are more spots revealed by grep, e.g. runqemu and
> sdk_ext. They just aren't automatically tested.
A change that worried me a lot was the removal of the custom ports as
it means only one client can run on a given system. I think that could
mean that we'd potentially hit issues if two tests ran on the same
build server. That is relatively unlikely but it is the kind of race
we've spent a lot of time removing on the autobuilder to avoid rare
failures. I didn't look further at the other patches being removed,
that one worried me alone.
Cheers,
Richard
next prev parent reply other threads:[~2022-11-22 15:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 13:31 [PATCH 01/17] elfutils: update 0.187 -> 0.188 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 02/17] rsync: update 3.2.5 -> 3.2.7 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 03/17] swig: update 4.0.2 -> 4.1.0 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 04/17] tcl: update 8.6.11 -> 8.6.12 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 05/17] unfs: update 0.9.22 -> 0.10.0 Alexander Kanavin
2022-11-22 12:29 ` [OE-core] " Richard Purdie
2022-11-22 15:03 ` Alexander Kanavin
2022-11-22 15:09 ` Richard Purdie [this message]
2022-11-22 15:13 ` Alexander Kanavin
2022-11-24 13:07 ` Alexander Kanavin
2022-11-24 13:44 ` Richard Purdie
2022-11-24 14:08 ` Alexander Kanavin
[not found] ` <172A8A8569CFF8A4.11309@lists.openembedded.org>
2022-11-25 11:49 ` Alexander Kanavin
2022-11-20 13:31 ` [PATCH 06/17] man-db: update 2.10.2 -> 2.11.1 Alexander Kanavin
2022-11-22 12:31 ` [OE-core] " Richard Purdie
2022-11-22 20:53 ` Alexander Kanavin
2022-11-22 22:16 ` Richard Purdie
2022-11-20 13:31 ` [PATCH 07/17] quota: update 4.06 -> 4.09 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 08/17] shadow: update 4.12.3 -> 4.13 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 09/17] texinfo: update 6.8 -> 7.0 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 10/17] libhandy: update 1.6.3 -> 1.8.0 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 11/17] xf86-input-mouse: update 1.9.3 -> 1.9.4 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 12/17] flac: update 1.4.0 -> 1.4.2 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 13/17] webkitgtk: update 2.36.7 -> 2.38.2 Alexander Kanavin
2022-11-22 15:21 ` [OE-core] " Richard Purdie
2022-11-24 12:23 ` Alexander Kanavin
2022-11-20 13:31 ` [PATCH 14/17] icu: update 71.1 -> 72-1 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 15/17] libgpg-error: update 1.45 -> 1.46 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 16/17] popt: update 1.18 -> 1.19 Alexander Kanavin
2022-11-20 13:31 ` [PATCH 17/17] vte: update 0.68.0 -> 0.70.1 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=ab2f02ff2654669a3c0b26bf741514698966b292.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--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