All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Cruz, Libertad" <libertad.cruz@intel.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"Jolley, Stephen K" <stephen.k.jolley@intel.com>,
	"Zhang, Jessica" <jessica.zhang@intel.com>,
	"juro.bystricky" <juro.bystricky@intel.com>
Cc: "Cruz Alcaraz, Juan M" <juan.m.cruz.alcaraz@intel.com>,
	"Jordan, Robin L" <robin.l.jordan@intel.com>
Subject: Re: QA cycle report for 2.2.2 rc2
Date: Fri, 15 Sep 2017 17:50:50 +0100	[thread overview]
Message-ID: <1505494250.18640.102.camel@linuxfoundation.org> (raw)
In-Reply-To: <58D9E2E50A021A45AD740492365FCDC532A24F9C@fmsmsx107.amr.corp.intel.com>

This is a tricky one to evaluate. Going through the bugs in the QA
report:

Bug 12075 - think this is ok to fix on the branch and release note
Bug 12080 - we think minimal eSDK never worked in morty therefore this 
            is a QA testing error?
Bug 12073 - we continue to see various gpg errors even with master, 
            propose not to block release on this and only fix master
Bug 12009 - resolved and already fixed in 2.2.2 (I marked it resolved)
Bug 11150 - was a bug with 2.2.1 but should be fixed in 2.2.2?
Bug 11611 - was this found in 2.2.2?
Bug 11064 - marked as resolved as per QA comment, fix was in 2.2.2
Bug 11597 - fix was added to 2.2.2 (marked as resolved)
Bug 10460 - open and unresolved with master but not release blocker IMO
Bug 11797 - can't see any backport but not a release blocker as the 
            source mirrors work
Bug 11109 - No backport afaict but not release blocker

Which leave us with 12081 to understand before we can decide whether to
release this or not.

So the decision to release or not depends on QA agreeing with the resolution of 12080 and figuring out what happened with 12081.

[Thanks to Ross for helping with some of this]

Cheers,

Richard




On Thu, 2017-09-14 at 16:53 -0700, Cruz, Libertad wrote:
> Here is the report for the 2.2.2 point release test cycle.
> Full Report :  https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-13_-
> _Full_Point_Release_Test_Cycle_2.2.2_rc2
> ======= Summary ========
> The QA cycle for point release 2.2.2 rc2 is complete.  There are 3
> new bugs: bug 12080[2]  blocks testing to the eSDK component since
> eSDK functionalities cannot be executed. Bugs 12075[1], 12073[3],
> 12081[4] don’t block full functionalities.
>  
> LPT results are waiting to be updated by Windriver.
>  
> Performance
> Compared with 2.2.2 rc1 there was a regression of 14.71 while
> building rootfs on Ubuntu, there was also a regression on Fedora
> while building sato of 7.46% and a regression on kernel of 12.12%.
>  
>  
> Ubuntu                 Test       2.2.2_rc1            
> 2.2.2_rc2             %
>                               sato       1:00:42             
> 1:01:16               0.93
>                               rootfs    2:16                   
> 2:36                     14.71
>                               rmwork 0:59:29              0:59:51  
>             0.62
>                               kernel    5:01                   
> 5:00                     -0.33
>                               eSDK      3:22                   
> 3:19                     -1.49
>                                                                      
>      
>                                                                      
>      
> Fedora                 Test       2.2.2_rc1            
> 2.2.2_rc2             %
>                               sato       1:01:55             
> 1:06:32               7.46
>                               rootfs    2:49                   
> 2:51                     1.18
>                               rmwork 0:59:52              1:01:32  
>             2.78
>                               kernel    6:03                   
> 6:47                     12.12
>                               eSDK      3:44                   
> 3:54                     4.46
>  
>  
> ptest
> There was an improvement on the pass rate in the following packages
> in comparison with 2.2.2 rc1:
> gdk-pixbuf with 5%
> libxml2 with 4.20%
> lttng-tools with 3.20%
>  
> On the other side there was a regression on the pass rate in
> comparison with 2.2.2 rc1:
> acl with 6.80%
> e2fsprogs with 100% regression
> gawk with .10%
> quilt with 1.80%
> valgrind of 53.10%
>  
>  
> Compliance
> Results are yet to be documented by Windriver.
>  
> ======= QA-Hints========
>  
> There is only one concern on the eSDK component it cannot execute. QA
> recommends an 2.2.2 rc3 to only verify the eSDK component.
>  
> ======= Bugs ========
>  
>        New Bugs
>             -12075[1]  [morty] testimage quemux86/qemux86-64 lsb
> tcgetattr: Input/output error^M
>             -12080[2] [Morty][Test Case 1605]
> TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make
>             -12073[3] selftest: setUpClass failed failing on ubuntu
> 17.04 (oeqa.selftest.signing.Signing)
>             -12081[4] [morty] PTEST: Package Name flex, gzip, slang,
> do not appear in 2.2.2 rc2
>  
> Full Bug Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-1
> 3_-_Full_Point_Release_Test_Cycle_2.2.2_rc2#Bugs_Found_during_QA_Test
>  
>  
> ======== Links =========
>  
>     1.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=12075 [1]
>     2.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=12080 [2]
>     3.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=12073 [3]
>     4.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=12081 [4]
>  
>    
>  
> Regards
> Libertad G.


  reply	other threads:[~2017-09-15 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 23:53 QA cycle report for 2.2.2 rc2 Cruz, Libertad
2017-09-15 16:50 ` Richard Purdie [this message]
2017-09-15 18:04   ` Bystricky, Juro
2017-09-15 19:50     ` Cruz, Libertad
2017-09-15 20:01       ` Bystricky, Juro
2017-09-15 20:06         ` akuster808
2017-09-15 20:14           ` Bystricky, Juro
2017-09-15 20:18             ` Cruz, Libertad

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=1505494250.18640.102.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jessica.zhang@intel.com \
    --cc=juan.m.cruz.alcaraz@intel.com \
    --cc=juro.bystricky@intel.com \
    --cc=libertad.cruz@intel.com \
    --cc=robin.l.jordan@intel.com \
    --cc=stephen.k.jolley@intel.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 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.