From: Denys Dmytriyenko <denis@denix.org>
To: Ross Burton <ross.burton@arm.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
"qa-build-notification@lists.yoctoproject.org"
<qa-build-notification@lists.yoctoproject.org>,
Yocto-mailing-list <yocto@lists.yoctoproject.org>,
Yocto TSC <tsc@lists.yoctoproject.org>
Subject: Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-5.0.rc2)
Date: Wed, 17 Apr 2024 12:53:34 -0400 [thread overview]
Message-ID: <20240417165334.GO28791@denix.org> (raw)
In-Reply-To: <A363D55A-F4F9-4764-AB3F-A919A39B41CC@arm.com>
On Wed, Apr 17, 2024 at 11:36:27AM +0000, Ross Burton wrote:
> On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:
> > For b), updating buildtools should resolve it, I thought I had done
> > that but there were a lot of moving pieces so I must not have got the
> > latest.
> >
> > I'm proposing we do but this into QA as I'd not block release on these
> > issues. I've done my best to get this into as good a shape as we can.
>
> Agreed. Can we do a build in the meantime of the specific job that failed
> so we can verify the buildtools/pip issue is resolved?
Sounds reasonable.
--
Denys
next prev parent reply other threads:[~2024-04-17 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:37 QA notification for completed autobuilder build (yocto-5.0.rc2) Pokybuild User
2024-04-17 8:50 ` [qa-build-notification] " Richard Purdie
2024-04-17 11:36 ` [tsc] " Ross Burton
2024-04-17 16:53 ` Denys Dmytriyenko [this message]
2024-04-17 21:23 ` Richard Purdie
[not found] ` <17C72E3BC41D08CD.20815@lists.yoctoproject.org>
2024-04-18 8:11 ` Richard Purdie
[not found] ` <908F7468-72EC-44F5-A083-6EC5716ACF64@arm.com>
2024-04-18 10:49 ` Richard Purdie
2024-04-18 15:45 ` Denys Dmytriyenko
2024-04-18 16:12 ` Richard Purdie
2024-04-17 17:24 ` Khem Raj
2024-04-18 1:09 ` Tham, Jing Hui
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=20240417165334.GO28791@denix.org \
--to=denis@denix.org \
--cc=qa-build-notification@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.