public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Stephen Jolley <sjolley.yp.pm@gmail.com>
Cc: Yocto-mailing-list <yocto@lists.yoctoproject.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Yocto Project Status 30 August 2022 (WW35)
Date: Tue, 30 Aug 2022 21:40:56 +0100	[thread overview]
Message-ID: <1792b01731d2412c53740470ba7521b68c6a3973.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-NE9s+b9Yny9+5q6MFGY3fT5RpWX76Sx6p-yFRGty1tw@mail.gmail.com>

On Tue, 2022-08-30 at 17:54 +0200, Alexander Kanavin wrote:
> On Tue, 30 Aug 2022 at 16:49, Stephen Jolley <sjolley.yp.pm@gmail.com> wrote:
> > layer setup changes didn’t test successfully
> 
> The latest patchset has no known issues.

I think I may be lagging a little behind on status. I did see a lot of
confusion about the patches and I know they didn't make the last
testing cut. Hopefully they'll be in the next patch.

> 
> > o    perl builds hanging indefinitely: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14902
> 
> I will look into this. Findings will go into the ticket.

Thanks! We haven't quite found the exact trigger to reproduce it but it
seems related to rebuilds somehow.

Cheers,

Richard



  reply	other threads:[~2022-08-30 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 14:49 Yocto Project Status 30 August 2022 (WW35) sjolley.yp.pm
2022-08-30 15:54 ` [OE-core] " Alexander Kanavin
2022-08-30 20:40   ` Richard Purdie [this message]
2022-08-30 21:14     ` Alexander Kanavin
2022-08-31  9:42     ` Alexander Kanavin
2022-08-31 11:16     ` 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=1792b01731d2412c53740470ba7521b68c6a3973.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sjolley.yp.pm@gmail.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