Yocto Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "qa-build-notification@lists.yoctoproject.org"
	<qa-build-notification@lists.yoctoproject.org>,
	Yocto discussion list <yocto@lists.yoctoproject.org>,
	Yocto TSC <tsc@lists.yoctoproject.org>,
	 Bruce Ashfield <bruce.ashfield@gmail.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3.rc1)
Date: Wed, 18 Oct 2023 20:43:57 +0100	[thread overview]
Message-ID: <0a3063a9d355acc42e5326e40539601f2d8dd145.camel@linuxfoundation.org> (raw)
In-Reply-To: <EF291923-E5FC-46CC-9AB4-291695AFABC2@arm.com>

On Wed, 2023-10-18 at 15:32 +0000, Ross Burton wrote:
> On 18 Oct 2023, at 07:29, Richard Purdie via lists.yoctoproject.org <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:
> > 
> > On Wed, 2023-10-18 at 06:16 +0000, Pokybuild User wrote:
> > >    A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder and is available at:
> > > 
> > > 
> > >        https://autobuilder.yocto.io/pub/releases/yocto-4.3.rc1
> > > 
> > > 
> > >    Build URL: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6062
> > 
> > There was one failure in the build, a serial login issue on ttyS1, so
> > an occurrence of our annoying 6.5 issue. This is the first time we've
> > seen it with the workaround applied.
> > 
> > The question is to proceed with rc1 in testing, or apply the upstream
> > fixes and try an rc2 with that? I'm torn…
> 
> I’d say we should proceed with RC1 whilst testing upstream fixes.
> 
> If they manage to shake out all of the failures then we can decide
> whether to spin another RC with the fixes in, or just release with
> what with have - with copious release notes obviously. 

Lets run with this approach, I agree. I am running test builds in the
background and we'll see how reliable the upstream fix is. I think
moving forward with rc1 as is makes sense.

Cheers,

Richard


  reply	other threads:[~2023-10-18 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18  6:16 QA notification for completed autobuilder build (yocto-4.3.rc1) Pokybuild User
2023-10-18  6:29 ` [qa-build-notification] " Richard Purdie
2023-10-18 15:32   ` [tsc] " Ross Burton
2023-10-18 19:43     ` Richard Purdie [this message]
2023-10-19  8:36 ` [yocto] " Alexis Lothoré
2023-10-19 11:04   ` Ross Burton
2023-10-19 12:28     ` Alexis Lothoré
2023-10-19 12:55       ` Richard Purdie
2023-10-19 12:23   ` Richard Purdie
2023-10-19 14:06 ` [qa-build-notification] " Tham, Jing Hui
2023-10-19 16:03   ` Richard Purdie

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=0a3063a9d355acc42e5326e40539601f2d8dd145.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Ross.Burton@arm.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=qa-build-notification@lists.yoctoproject.org \
    --cc=tsc@lists.yoctoproject.org \
    --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