Hi Armin, Thanks for informing. I didn’t receive any mail for zeus-rc3. As agreed earlier, QA team is not running test cycle for zeus-rc3. I have verified ptest results for rc3, “bash.run-glob-test” is passing. Also, no new ptest failures in rc3.
Thanks, Sangeeta From: akuster808 <akuster...@gmail.com> Sent: Friday, 21 February, 2020 11:38 PM To: Jain, Sangeeta <sangeeta.j...@intel.com>; Richard Purdie <richard.pur...@linuxfoundation.org>; Mittal, Anuj <anuj.mit...@intel.com>; yocto@lists.yoctoproject.org Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv <apoorv.san...@intel.com>; Yeoh, Ee Peng <ee.peng.y...@intel.com>; Chan, Aaron Chun Yew <aaron.chun.yew.c...@intel.com>; sjolley.yp...@gmail.com; Tummalapalli, Vineela <vineela.tummalapa...@intel.com> Subject: Re: [yocto] QA Cycle report for build (yocto-3.0.2.rc2) Jain, On 2/20/20 5:57 PM, Jain, Sangeeta wrote: From: akuster <akus...@mvista.com><mailto:akus...@mvista.com> Sent: Friday, 21 February, 2020 7:01 AM To: Richard Purdie <richard.pur...@linuxfoundation.org><mailto:richard.pur...@linuxfoundation.org>; Jain, Sangeeta <sangeeta.j...@intel.com><mailto:sangeeta.j...@intel.com>; Mittal, Anuj <anuj.mit...@intel.com><mailto:anuj.mit...@intel.com>; akuster808 <akuster...@gmail.com><mailto:akuster...@gmail.com>; yocto@lists.yoctoproject.org<mailto:yocto@lists.yoctoproject.org> Cc: ota...@ossystems.com.br<mailto:ota...@ossystems.com.br>; yi.z...@windriver.com<mailto:yi.z...@windriver.com>; Sangal, Apoorv <apoorv.san...@intel.com><mailto:apoorv.san...@intel.com>; Yeoh, Ee Peng <ee.peng.y...@intel.com><mailto:ee.peng.y...@intel.com>; Chan, Aaron Chun Yew <aaron.chun.yew.c...@intel.com><mailto:aaron.chun.yew.c...@intel.com>; sjolley.yp...@gmail.com<mailto:sjolley.yp...@gmail.com>; Tummalapalli, Vineela <vineela.tummalapa...@intel.com><mailto:vineela.tummalapa...@intel.com> Subject: Re: [yocto] QA Cycle report for build (yocto-3.0.2.rc2) On 2/20/20 2:44 PM, Richard Purdie wrote: I discussed this quickly in bug triage today with Armin. We agreed that: * The openssh bug is minor and doesn't affect release * Anuj resolved one of the bugs as being execution error so again it doesn't affect release * The bash issue does affect release We're proposing we build and release an rc3 with the bash CVE reverted. This would also include the bitbake memory optimisation during parsing which merged. We wouldn't rerun the manual QA for rc3, just check the automated test results. Does anyone have any objection to that? If not, QA should see an rc3 email but we're just expecting to check the test results if that works for everyone? Works for me. Sound good from QA perspective. Verifying automated test results and ptest results should be good. Zeus-rc3 finished. the QA email failed to send. - armin Vineela: Not sure how this affects release process, we'll just have to figure that out. List them as Known issues? Release should be done on rc3. Status of bugs can be updated in ‘header-intel.txt’. Just my thoughts! - armin Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48578): https://lists.yoctoproject.org/g/yocto/message/48578 Mute This Topic: https://lists.yoctoproject.org/mt/71391111/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
