[QA] Release Meeting 2011-12-09

[Patrick Wright]

On Fri, Dec 9, 2011 at 5:12 PM, Jean-Baptiste Lallement
<jean-baptiste at ubuntu.com> wrote:
> On 12/09/2011 09:11 PM, Steve Langasek wrote:
>>
>> Hi Jean-Baptiste,
>
> Hi Steve,
>
>> On Fri, Dec 09, 2011 at 09:34:43AM +0100, Jean-Baptiste Lallement wrote:
>>>
>>>  * Boot Speed testing
>>>    * Daily boot speed testing run on Desktop i386
>>>    * Report: http://reports.qa.ubuntu.com/reports/boot-speed/
>>
>>
>> Today's test for the Dell Vostro shows that ureadahead is not preloading
>> files as intended:
>>
>>
>> http://reports.qa.ubuntu.com/reports/boot-speed/dell-vostro-3400/2011-12-09_09-59-00/bootchart.png
>>
>> This could be due to either a bug in ureadahead or a bug in the test
>> configuration.  (It does not appear to be caused by using an SSD; looking
>> at
>> the device name listed in dmesg, this seems to be a rotational disk model.
>> It would probably be helpful if this information were easily visible in
>> some
>> sort of summary of the machine information.)
If the info you require isn't listed in lspci file please provide me
with what specific data would be helpful to add. Providing the command
with options would be most helpful to me.

>>
>> Is the methodology used for boot speed testing described somewhere?  I'd
>> like to try to reproduce this and figure out what's happening.  Not having
>> ureadahead working correctly causes a huge amount of noise in boot charts;
>> for instance, today's chart shows lightdm hitting the disk for a full
>> second
>> before it gets around to starting X (which gets counted against the
>> plumbing
>> budget), and this almost entirely accounts for the difference in plumbing
>> time in yesterday's run vs. today's on this machine.  There's no way to
>> tell from the currently available info if this is a regression in lightdm,
>> or just noise as a result of ureadahead not running correctly.

Automation aside, its really simple if you want to do this manually.
1. Get the latest daily iso (desktop or alternate)
2. Install from iso
3. Install bootchart package on startup
4. Reboot again
5. Check bootchart results

You can add debugging to dmesg if that will provide information useful to you.

>
>
> I'm CC'ing Patrick who set up and maintains the test for the QA Team and can
> provide all the details.
>
>>
>> Thanks,
>
>
>
> --
> Jean-Baptiste
> irc: jibel