Hi Michael,

For the kernel and gcc information, after board booted up, we can just run:

1. uname -a
2. gcc --version

Then grab a part of output string, that's it.

For the boot and serial test, if we don't think comprehensively, then we can say if 1 and 2 can be executed successfully and we have got output string from it, then boot and serial test can be considered passed.

Idea?

Thanks.


Best Regards
Botao Sun

On Mon, Jan 28, 2013 at 10:34 AM, Michael Hudson-Doyle <michael.hudson@linaro.org> wrote:
Andy Doan <andy.doan@linaro.org> writes:

> + Michael - he's the expert on this.
>
> On 01/25/2013 01:02 AM, Botao Sun wrote:
>> Hi Fathi & Andy,
>>
>> I'm wondering that can we show more information on our Linux Linaro
>> ubuntu daily test dashboard? I'm looking at our weekly manual test on
>> these images and find that some test cases can be covered by our
>> existing daily test with some minor modifications. For example, TI Panda
>> 4460 board:
>>
>> [1]
>> http://validation.linaro.org/lava-server/dashboard/image-reports/linux-linaro-tracking-panda-es
>>
>> For our weekly manual test:
>>
>> [2]
>> https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZkhrZ1VYUEg2LTlQZzR0RlhzM3c#gid=4
>>
>> We fill kernel and gcc version in spreadsheet, perhaps we can just show
>> these information on link [1].

If this information can be reported to lava some how (a test run
attribute?) then I think it should be easy enough and a good feature to
write some code to display it on the image report page.

>> Also, if board can boot up successfully, then test case "boot" &
>> "serial" can be considered passed, and we can just add 2 extra rows
>> for these 2 test cases.

This seems a bit harder.  I have a little nagging thing in my brain
about how boot testing is sort of implicitly tested / reported at the
moment, which might be the better thing to fix...

Cheers,
mwh