From: "Khem Raj" <raj.khem@gmail.com>
To: Armpit <akuster808@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
"Jain, Sangeeta" <sangeeta.jain@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Yocto TSC <tsc@lists.yoctoproject.org>,
"Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>
Cc: "otavio@ossystems.com.br" <otavio@ossystems.com.br>,
"yi.zhao@windriver.com" <yi.zhao@windriver.com>,
"Sangal, Apoorv" <apoorv.sangal@intel.com>,
"Yeoh, Ee Peng" <ee.peng.yeoh@intel.com>,
"Chan, Aaron Chun Yew" <aaron.chun.yew.chan@intel.com>,
"sjolley.yp.pm@gmail.com" <sjolley.yp.pm@gmail.com>
Subject: Re: [tsc] QA Cycle report for build (yocto-3.1_M1.rc8)
Date: Wed, 18 Dec 2019 12:46:30 -0800 [thread overview]
Message-ID: <f6dc629b-a1d7-76cf-25f8-dccdae0f0902@gmail.com> (raw)
In-Reply-To: <758d70c1-e964-483a-a0ee-69763fea3d9c@gmail.com>
On 12/18/19 7:38 AM, Armpit wrote:
>
>
> On 12/18/19 2:46 AM, Richard Purdie wrote:
>> On Wed, 2019-12-18 at 03:32 +0000, Jain, Sangeeta wrote:
>>> Hello all,
>>>
>>> This is the full report for 3.1_M1.rc8:
>>> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
>>>
>>>
>>> ======= Summary ========
>>> No high milestone defects.
>>> No new defects are found in this cycle.
>>> glib and valgrind ptest failed (BUG id:13713).
>
> The Valgrind is a known issue:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13666
>
>>>
>>> ======= Bugs ========
>>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13713
>> Thanks Sangeeta.
>>
>> Adding TSC to CC.
>>
>> We have the bugs above but they're minor ptest issues (small
>> regressions).
>>
>> We have performance problems in certain world build cases but we need
>> to work through those issues in master.
>>
>> We also have reproducibile build issues but those are in theory fixed
>> in master.
>>
>> I think we should ship this as I can't see any huge improvements from
>> any further respins, it just collides with vactions. We should move
>> forward to M2 after the holidays.
>
> I would make these blockers for M2/M3 and approve shipping M1
>
I would also agree to ship M1 without this.
> - armin
>>
>> Cheers,
>>
>> Richard
>>
>>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#247): https://lists.yoctoproject.org/g/tsc/message/247
> Mute This Topic: https://lists.yoctoproject.org/mt/68790744/1997914
> Group Owner: tsc+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/tsc/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2019-12-18 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 3:32 QA Cycle report for build (yocto-3.1_M1.rc8) Sangeeta Jain
2019-12-18 4:11 ` Armpit
2019-12-18 5:18 ` Sangeeta Jain
2019-12-18 10:46 ` Richard Purdie
2019-12-18 15:38 ` Armpit
2019-12-18 20:46 ` Khem Raj [this message]
2019-12-18 20:57 ` [tsc] " Denys Dmytriyenko
2019-12-19 11: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=f6dc629b-a1d7-76cf-25f8-dccdae0f0902@gmail.com \
--to=raj.khem@gmail.com \
--cc=aaron.chun.yew.chan@intel.com \
--cc=akuster808@gmail.com \
--cc=apoorv.sangal@intel.com \
--cc=ee.peng.yeoh@intel.com \
--cc=otavio@ossystems.com.br \
--cc=richard.purdie@linuxfoundation.org \
--cc=sangeeta.jain@intel.com \
--cc=sjolley.yp.pm@gmail.com \
--cc=tsc@lists.yoctoproject.org \
--cc=vineela.tummalapalli@intel.com \
--cc=yi.zhao@windriver.com \
--cc=yocto@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