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-linar...
For our weekly manual test:
[2]
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZk...
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
On 01/27/2013 09:26 PM, Botao Sun wrote:
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...
I agree. Maybe lava-test-shell could add some sort of "boot passed" test result once it sees the prompt and before it executes the shell stuff?
Yes, if it shows "root@localhost:~#" in serial console, then we can reasonably say "boot" and "serial" test passed. Or we can move a little bit forward, if "uname -a" works well and we got the output string, we can say "serial" test *actually* passed.
Best Regards Botao Sun
On Mon, Jan 28, 2013 at 3:00 PM, Andy Doan andy.doan@linaro.org wrote:
On 01/27/2013 09:26 PM, Botao Sun wrote:
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...
I agree. Maybe lava-test-shell could add some sort of "boot passed" test result once it sees the prompt and before it executes the shell stuff?
Andy Doan andy.doan@linaro.org writes:
On 01/27/2013 09:26 PM, Botao Sun wrote:
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...
I agree. Maybe lava-test-shell could add some sort of "boot passed" test result once it sees the prompt and before it executes the shell stuff?
Maybe this should be added to the lava test run? I think that would be easy enough, actually. I don't like the idea of adding it to whatever test run happens to be executed by lava-test-shell...
Botao Sun botao.sun@linaro.org writes:
Hi Michael,
For the kernel and gcc information, after board booted up, we can just run:
- uname -a
- gcc --version
Then grab a part of output string, that's it.
These could be added as test run attributes. There's no API for doing this yet and no way of showing them on the image report but neither part of that would be very hard.
Hi Michael,
OK, understood. Yes, it's unnecessary to add these information to every test run by lava-test-shell. What my original thought is to show kernel and gcc version on our dashboard then everyone can get these information quickly and don't need to find them inside serial log output.
But since it will be difficult to do, then I will just write command to get these information and redirect it to a text file for further parsing usage.
Thanks.
Best Regards Botao Sun
On Wed, Jan 30, 2013 at 12:42 PM, Michael Hudson-Doyle < michael.hudson@linaro.org> wrote:
Botao Sun botao.sun@linaro.org writes:
Hi Michael,
For the kernel and gcc information, after board booted up, we can just
run:
- uname -a
- gcc --version
Then grab a part of output string, that's it.
These could be added as test run attributes. There's no API for doing this yet and no way of showing them on the image report but neither part of that would be very hard.
Botao Sun botao.sun@linaro.org writes:
Hi Michael,
OK, understood. Yes, it's unnecessary to add these information to every test run by lava-test-shell. What my original thought is to show kernel and gcc version on our dashboard then everyone can get these information quickly and don't need to find them inside serial log output.
But since it will be difficult to do, then I will just write command to get these information and redirect it to a text file for further parsing usage.
That's probably best for now. We'll do better eventually :-)
linaro-validation@lists.linaro.org
-
Andy Doan -
Botao Sun -
Michael Hudson-Doyle