From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: qa-build-notification@lists.yoctoproject.org,
Pokybuild User <pokybuild@centos8-ty-1.yocto.io>
Cc: yocto@lists.yoctoproject.org, "Tummalapalli,
Vineela" <vineela.tummalapalli@intel.com>,
Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [qa-build-notification] [yocto] QA notification for completed autobuilder build (yocto-3.2.2.rc1)
Date: Thu, 18 Feb 2021 14:03:44 +0000 [thread overview]
Message-ID: <25b42e0ef16cfed0d70ce2bd47ff971102a93a8b.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+4=imb+CNt9fZgUOMY8f+4Kcat+=rUAqGt5pbHDRZxQ-7M5CQ@mail.gmail.com>
On Thu, 2021-02-18 at 14:58 +0100, Yann Dirson wrote:
>
>
> Le mar. 16 févr. 2021 à 18:43, Pokybuild User <pokybuild@centos8-ty-1.yocto.io> a écrit :
> >
> > Build hash information:
> >
> > bitbake: 0a3bf681530bd63fc0036ca81ef868ab53fde56c
> > meta-arm: aa63e31b6edb5197764c21434219050ab51f0fbd
> > meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
> > meta-intel: 1d866c58534eb1d317b7a674c6e6c57ab9594fb0
> > meta-kernel: f793168bd19af3d8c5a260dd35f387ed9a31794b
> > meta-mingw: 352d8b0aa3c7bbd5060a4cc2ebe7c0e964de4879
> > oecore: ebaaee50cb3ac75112827f935c48affaf622ce7f
> > poky: d5d6286a66f46f4523e35e0e3f20cd7396195fdc
> >
>
> Is it expected that the noted meta-arm sha1 is on branch "master" and not "gatesgarth" ?
Not expected but we worked it out. There is a patch from Ross on
this list which fixes the issue in yocto-autobuilder2. For the
purposes of the release I'm thinking we should rerun the meta-arm
tests and swap in the gatesgarth revision.
Copying Vineela/Michael so they know about the issue.
Cheers,
Richard
next prev parent reply other threads:[~2021-02-18 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 17:43 QA notification for completed autobuilder build (yocto-3.2.2.rc1) Pokybuild User
2021-02-18 3:54 ` [yocto] " Sangeeta Jain
2021-02-18 13:58 ` Yann Dirson
2021-02-18 14:03 ` Richard Purdie [this message]
2021-02-22 6:27 ` Sangeeta Jain
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=25b42e0ef16cfed0d70ce2bd47ff971102a93a8b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mhalstead@linuxfoundation.org \
--cc=pokybuild@centos8-ty-1.yocto.io \
--cc=qa-build-notification@lists.yoctoproject.org \
--cc=vineela.tummalapalli@intel.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.