From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Yeoh, Ee Peng" <ee.peng.yeoh@intel.com>,
"Cruz, Libertad" <libertad.cruz@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Lock, Joshua G" <joshua.g.lock@intel.com>,
"Jolley, Stephen K" <stephen.k.jolley@intel.com>,
"Zhang, Jessica" <jessica.zhang@intel.com>
Cc: "Sangal, Apoorv" <apoorv.sangal@intel.com>,
"Perez Carranza, Jose" <jose.perez.carranza@intel.com>
Subject: Re: QA cycle report for 2.4.1 RC1
Date: Tue, 02 Jan 2018 11:26:33 +0000 [thread overview]
Message-ID: <1514892393.5525.69.camel@linuxfoundation.org> (raw)
In-Reply-To: <9DDD2658D1FE414E99172D2DB1E4D04335D94DFF@PGSMSX109.gar.corp.intel.com>
Hi,
On Fri, 2017-12-22 at 01:40 -0800, Yeoh, Ee Peng wrote:
> Enjoy viewing the full Report for 2.4.1
> RC1: https://wiki.yoctoproject.org/wiki/WW51_-_2017-12-21-
> _Full_Test_Cycle_-_2.4.1_rc1
>
> ======= Summary ========
>
> The QA cycle for release 2.4.1 RC1 is complete. There are 5 new bugs
> from which so far none of them are high. QA has 1 concern on the
> performance testing.
>
> Performance report shows an increase of 23% build time on the eSDK in
> fedora 23, bug has not been created until further investigation with
> setup outside of the GDC environment.
Was there any further update on this?
It may be worth running the test for 2.4.0 and checking that you get
the same result as we had at time of release, just to double check
there isn't some other contributing cause here...
Cheers,
Richard
next prev parent reply other threads:[~2018-01-02 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 9:40 QA cycle report for 2.4.1 RC1 Yeoh, Ee Peng
2018-01-02 11:26 ` Richard Purdie [this message]
2018-01-03 2:11 ` Yeoh, Ee Peng
2018-01-03 13:41 ` Perez Carranza, Jose
2018-01-05 9:21 ` Yeoh, Ee Peng
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=1514892393.5525.69.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=apoorv.sangal@intel.com \
--cc=ee.peng.yeoh@intel.com \
--cc=jessica.zhang@intel.com \
--cc=jose.perez.carranza@intel.com \
--cc=joshua.g.lock@intel.com \
--cc=libertad.cruz@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.