From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bill Mills <bill.mills@linaro.org>, yocto@lists.yoctoproject.org
Cc: "ilias.apalodimas@linaro.org" <ilias.apalodimas@linaro.org>,
Mikko Rapeli <mikko.rapeli@linaro.org>,
Lee Chee Yang <chee.yang.lee@intel.com>,
Jing Hui Tham <jing.hui.tham@intel.com>,
Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-5.0.1.rc1)
Date: Thu, 09 May 2024 20:54:44 +0100 [thread overview]
Message-ID: <dea1bd7c2fa74c871185acfe1734c3eda6c2c4f5.camel@linuxfoundation.org> (raw)
In-Reply-To: <800eeeed-19e1-4b10-aab5-34f5c4a9d51c@linaro.org>
On Thu, 2024-05-09 at 13:21 -0400, Bill Mills wrote:
> Richard / Steve / All,
>
> On 5/8/24 10:12 AM, Richard Purdie via lists.yoctoproject.org wrote:
> > On Wed, 2024-05-08 at 14:06 +0000, Pokybuild User via
> > lists.yoctoproject.org wrote:
> > >
> > > A build flagged for QA (yocto-5.0.1.rc1) was completed on
> > > the
> > > autobuilder and is available at:
> > >
> > >
> > >
> > > https://autobuilder.yocto.io/pub/releases/yocto-5.0.1.rc1
> > >
> > >
> > > Build URL:
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6885
> > >
> >
> > From discussions with Steve, I think due to failures in this build
> > we're trying an rc2.
>
> We are looking for a pipe cleaner for automated machine tests.
> If this is DOA we probibly don't want to use it correct?
There are a few QA failures but they're intermittent issues and it was
marginal whether to rebuild or not. For a pipe cleaner it would be
fine.
> Unfortunately the 5.0 rc4 release is no longer on the autobuilder.
> (But rc1 rc2 and rc3 still are). [1] How long are they kept and when
> are they deleted?
When an rc is promoted to a release it is removed (or moved) as part of
the transition so rc4 became the release. We clean up old obsolete ones
when we remember or are short on space on the NAS.
> Is the dir structure of the release [2] the exact same as the rcN?
I'm not 100% sure. It used to vary and I've been trying to get us to
match, I don't know where we currently stand. Copying Chee Yang and
Jing Hui who would know along with Michael.
> It appears so on first glance. Did rc4 get mv'ed instead of cp'ed?
> Is this the expected behavior?
It is what happens during the publishing process.
Cheers,
Richard
prev parent reply other threads:[~2024-05-09 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 14:06 QA notification for completed autobuilder build (yocto-5.0.1.rc1) Pokybuild User
2024-05-08 14:12 ` [qa-build-notification] " Richard Purdie
2024-05-09 17:21 ` [yocto] " Bill Mills
2024-05-09 19:54 ` 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=dea1bd7c2fa74c871185acfe1734c3eda6c2c4f5.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bill.mills@linaro.org \
--cc=chee.yang.lee@intel.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jing.hui.tham@intel.com \
--cc=mhalstead@linuxfoundation.org \
--cc=mikko.rapeli@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).