public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Jain, Sangeeta" <sangeeta.jain@intel.com>,
	 "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Cc: "otavio@ossystems.com.br" <otavio@ossystems.com.br>,
	 "yi.zhao@windriver.com" <yi.zhao@windriver.com>,
	"Sangal, Apoorv" <apoorv.sangal@intel.com>,
	"Chan, Aaron Chun Yew" <aaron.chun.yew.chan@intel.com>,
	"akuster808@gmail.com" <akuster808@gmail.com>,
	 "sjolley.yp.pm@gmail.com" <sjolley.yp.pm@gmail.com>,
	"Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>,
	"Teoh, Jay Shen" <jay.shen.teoh@intel.com>
Subject: Re: [yocto] QA notification for completed autobuilder build (yocto-3.2.rc1)
Date: Mon, 26 Oct 2020 22:36:26 +0000	[thread overview]
Message-ID: <6bc8b75acf70346af53db04dbb84284e4571ee8a.camel@linuxfoundation.org> (raw)
In-Reply-To: <BYAPR11MB3624C502B36E80A6A1BBCB41E3190@BYAPR11MB3624.namprd11.prod.outlook.com>

On Mon, 2020-10-26 at 07:06 +0000, Jain, Sangeeta wrote:
> Hello all,
> 
> This is the full report for yocto-3.2.rc1:  
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
> 
> ======= Summary ========
> No new defects are found.
> No high milestone defects.
> 
> glib-2.0 ptest failed (BUG id:14106)
>   
> Bugs verified:
> 
> BUG id:14050 - [QA 3.2 M3 RC1] failure in ptest : parted component
>    Verified Fixed.
> 
> Existing bugs observed in this release:
> 
> valgrind ptest failed (BUG id:14051)
>    Updated with 2 ptests passed and 3 new failures.
>   
> ======= Bugs ========
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14106
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14050
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14051

Thanks for this Sangeeta and team!

Since this is final 3.2 we're keen to ensure we sort out the issues we
can. There was a buildhistory issue that became apparent in the last
few days. Adding in the above two ptest issues and we probably can't
release rc1.

I've merged fixes for the buildhistory issue and both the glib-2.0 and
valgrind ptest issues along with some other small tweaks and have
triggered a build of rc2.

Cheers,

Richard




      reply	other threads:[~2020-10-26 22:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201020163538.0C38244D07F@centos7-ty-4.yocto.io>
2020-10-21  3:34 ` [yocto] QA notification for completed autobuilder build (yocto-3.2.rc1) Sangeeta Jain
2020-10-26  7:06 ` Sangeeta Jain
2020-10-26 22:36   ` 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=6bc8b75acf70346af53db04dbb84284e4571ee8a.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=aaron.chun.yew.chan@intel.com \
    --cc=akuster808@gmail.com \
    --cc=apoorv.sangal@intel.com \
    --cc=jay.shen.teoh@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=sangeeta.jain@intel.com \
    --cc=sjolley.yp.pm@gmail.com \
    --cc=vineela.tummalapalli@intel.com \
    --cc=yi.zhao@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox