From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>
Cc: Joshua Watt <jpewhacker@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto][meta-mingw][PATCH] oeqa: Set LANG in wine tests
Date: Tue, 25 Feb 2025 16:53:30 +0000 [thread overview]
Message-ID: <9ee46ddb0ffbab94b2015eb81e711845be9b4471.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAOSpxdZT+tuqP0CmKUrZR7W+i6-2PPuHwWcdk33_48R-1c66Pw@mail.gmail.com>
On Tue, 2025-02-25 at 08:29 -0800, Steve Sakoman wrote:
> On Wed, Oct 30, 2024 at 9:03 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > On Wed, 2024-10-30 at 10:02 -0600, Joshua Watt wrote:
> > > On Wed, Oct 30, 2024 at 9:18 AM Steve Sakoman <steve@sakoman.com>
> > > wrote:
> > > >
> > > > Would it be possible to cherry-pick this commit to the styhead
> > > > branch?
> > > > I'm seeing the same issue there.
> > >
> > > Yes, that would be a good idea. It's based on the build host, not
> > > wine
> > > or Yocto, so I suspect we would see it on any branch using that
> > > host.
> > >
> > > Pretty sure it will cherry-pick cleanly, do you want me to send a
> > > patch?
> >
> > I've sorted it, thanks.
>
> Looks like this was backported to kirkstone and styhead, but not
> scarthgap.
>
> I'm seeing scarthgap meta-mingw failures when running on Ubuntu 24.04
> workers.
>
> Can we backport to scarthgap too?
Done.
Cheers,
Richard
prev parent reply other threads:[~2025-02-25 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 22:54 [yocto][meta-mingw][PATCH] oeqa: Set LANG in wine tests Joshua Watt
2024-10-30 15:18 ` Steve Sakoman
2024-10-30 16:02 ` Joshua Watt
2024-10-30 16:03 ` Richard Purdie
2025-02-25 16:29 ` Steve Sakoman
2025-02-25 16:53 ` Richard Purdie [this message]
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=9ee46ddb0ffbab94b2015eb81e711845be9b4471.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jpewhacker@gmail.com \
--cc=steve@sakoman.com \
--cc=yocto@lists.yoctoproject.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