From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: qa-build-notification@lists.yoctoproject.org,
yocto@lists.yoctoproject.org
Cc: Yocto TSC <tsc@lists.yoctoproject.org>,
Bruce Ashfield <bruce.ashfield@gmail.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3.rc1)
Date: Wed, 18 Oct 2023 07:29:26 +0100 [thread overview]
Message-ID: <40ab5c11d917f68dc6115d24f2fd427cb4a1fd38.camel@linuxfoundation.org> (raw)
In-Reply-To: <0101018b416d8d29-59a72af7-335c-4677-b485-bc0ec3abd261-000000@us-west-2.amazonses.com>
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...
Cheers,
Richard
next prev parent reply other threads:[~2023-10-18 6:29 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 ` Richard Purdie [this message]
2023-10-18 15:32 ` [tsc] [qa-build-notification] " Ross Burton
2023-10-18 19:43 ` Richard Purdie
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=40ab5c11d917f68dc6115d24f2fd427cb4a1fd38.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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