Machine was rebooted
last week 12/12
-$ who -b
system boot 2017-12-12 09:18
-$ uptime -s
2017-12-12 09:19:28
-----Original Message-----
From: Perez Carranza, Jose
Sent: Thursday, December 21, 2017 8:57 AM
To: Purdie, Richard <richard.pur...@intel.com>; Cruz, Libertad
<libertad.c...@intel.com>; yocto@yoctoproject.org; Lock, Joshua G
<joshua.g.l...@intel.com>; Jolley, Stephen K <stephen.k.jol...@intel.com>;
Zhang, Jessica <jessica.zh...@intel.com>
Cc: Sangal, Apoorv <apoorv.san...@intel.com>; Yeoh, Ee Peng
<ee.peng.y...@intel.com>
Subject: Re: QA cycle report for 2.3.3 RC1
On 12/21/2017 08:43 AM, Richard Purdie wrote:
> On Wed, 2017-12-20 at 20:25 -0800, Cruz, Libertad wrote:
>> Hello All,
>> Enjoy viewing the full Report for 2.3.3 RC1: https://wiki.yoctoproje
>> ct.org/wiki/WW51_-_2017-12-20-_Full_Test_Cycle_-_2.3.3_rc1
>>
>> ======= Summary ========
>>
>> The QA cycle for release 2.3.3 RC1 is complete. There are 4 new bugs
>> from which so far none of them are high. QA has two big concerns:
>>
>> 1. Performance report shows an increase of 30% build time
>> on the eSDK in fedora 23, bug has not been created until further
>> investigation with setup outside of the GDC environment.
> Could you confirm when the performance test machines were last
> rebooted? We've had issues before where the benchmarks drift with
> machine uptime. If the've been running for more than about 3 weeks I'd
> like to run the benchmarks again after a reboot.
It was last week 12/12
-$ who -b
system boot 2017-12-12 09:18
-$ uptime -s
2017-12-12 09:19:28
> Thanks!
>
> Richard
--
Saludos
José
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
