All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: qa-build-notification@lists.yoctoproject.org,
	yocto@lists.yoctoproject.org
Cc: Steve Sakoman <steve@sakoman.com>
Subject: Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.0.2.rc1)
Date: Wed, 29 Jun 2022 13:43:30 +0100	[thread overview]
Message-ID: <7afd34dca0455a0561ca80e30049f7fbde1a11b0.camel@linuxfoundation.org> (raw)
In-Reply-To: <01010181af49cc59-7fa1b027-722d-4360-9ca4-4894f160087e-000000@us-west-2.amazonses.com>

On Wed, 2022-06-29 at 11:47 +0000, Pokybuild User wrote:
> A build flagged for QA (yocto-4.0.2.rc1) was completed on the autobuilder and is available at:
> 
> 
>     https://autobuilder.yocto.io/pub/releases/yocto-4.0.2.rc1
> 
> 
> Build hash information: 
> 
> bitbake: b8fd6f5d9959d27176ea016c249cf6d35ac8ba03
> meta-agl: c4cc627f4d65da8c3b0860c791d9b9687ba8f5d6
> meta-arm: af928569b421431347c84f5941cee7aaa9f0ac74
> meta-aws: 8b8eec4bde3b1ff00783503bd77b3a5fb7d904ec
> meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a
> meta-intel: ef3aa3064b9bbfa19f600eafb1e7d3473f62af74
> meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1
> meta-openembedded: fcc7d7eae82be4c180f2e8fa3db90a8ab3be07b7
> meta-virtualization: 320f44c6e9af463a85b58e0d87ca70273c6b87f6
> oecore: eea52e0c3d24c79464f4afdbc3c397e1cb982231
> poky: a5ea426b1da472fc8549459fff3c1b8c6e02f4b5
> 

There were two failures in the build on the autobuilder, both are due
to known scp issues with fedora36. I thought we hadn't enabled
kirkstone on f36 but evidently we have :/.

I don't believe the two issues should block 4.0.2 testing or release.

Cheers,

Richard


  reply	other threads:[~2022-06-29 12:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 11:47 QA notification for completed autobuilder build (yocto-4.0.2.rc1) Pokybuild User
2022-06-29 12:43 ` Richard Purdie [this message]
2022-06-29 13:50   ` [qa-build-notification] " Steve Sakoman
2022-07-01  3:51 ` Teoh, Jay Shen
2022-07-05  4:33 ` Teoh, Jay Shen

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=7afd34dca0455a0561ca80e30049f7fbde1a11b0.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=qa-build-notification@lists.yoctoproject.org \
    --cc=steve@sakoman.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 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.