Hi Linaro folks,
I'd like to set up an automated testing environment to help me maintain the MMC subsystem: just a few boards of different architectures booting each day's linux-next and running basic performance and integrity tests without any manual intervention involved. I've got access to remote power switches, so I think it'll be pretty easy to get running.
I was thinking that this will probably find generic kernel bugs as they appear in linux-next, and was wondering whether Linaro has any interest in such testing -- if so, do you have any preferred software to use for it, or any resources I should take a look at to avoid duplicating work? I've been looking at using autotest, but it seems a bit abandoned lately.
Would be grateful for any pointers or ideas. Thanks!
- Chris.
Hi Chris, we actually have a project in progress called LAVA to do something very similar to this. Our initial target is to test full linaro images and hardware packs, however we are also very interested in extending this to include running with just an updated kernel in a known good image to test things like upstream and landing team kernels. I'm away from my computer right now, but I would be very intersted in having your input on this if you are interested. I should be around later this evening or tomorrow if you'd like to chat further on irc. Look for plars on freenode.
Thanks, Paul Larson On Apr 6, 2011 6:50 PM, "Chris Ball" cjb@laptop.org wrote:
Hi Linaro folks,
I'd like to set up an automated testing environment to help me maintain the MMC subsystem: just a few boards of different architectures booting each day's linux-next and running basic performance and integrity tests without any manual intervention involved. I've got access to remote power switches, so I think it'll be pretty easy to get running.
I was thinking that this will probably find generic kernel bugs as they appear in linux-next, and was wondering whether Linaro has any interest in such testing -- if so, do you have any preferred software to use for it, or any resources I should take a look at to avoid duplicating work? I've been looking at using autotest, but it seems a bit abandoned lately.
Would be grateful for any pointers or ideas. Thanks!
- Chris.
-- Chris Ball cjb@laptop.org http://printf.net/ One Laptop Per Child
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
I'm curious; do we have any interaction with the autotest project - it seems it's whole point is automated kernel testing,. http://autotest.kernel.org/ and test.kernel.org
Dave
On Thu, Apr 7, 2011 at 3:24 AM, David Gilbert david.gilbert@linaro.org wrote:
I'm curious; do we have any interaction with the autotest project - it seems it's whole point is automated kernel testing,. http://autotest.kernel.org/ and test.kernel.org
I did some looking at it, but what we are trying to provide is much bigger than just kernel testing by itself. That being said, I think some of the tests in the autotest client would be useful to run. There's a couple of ways we could do it. The preference would be to pick the important ones, and enable abrek to work with them. We could also possibly look at running the autotest client directly under lava, but would require a bit of extra work to get the results into the right format.
Thanks, Paul Larson
Hi David,
On Thu, Apr 07 2011, David Gilbert wrote:
I'm curious; do we have any interaction with the autotest project
- it seems it's whole point is automated kernel testing,.
http://autotest.kernel.org/ and test.kernel.org
test.kernel.org hasn't done anything since around 2.6.36 -- I think it was run by Martin Bligh (one of the autotest authors) when he worked at Google, but he's not there anymore and isn't working on autotest now.
There's a similar question as to whether autotest itself is still being developed. It does at least have some large industry users sending in patches, but there doesn't seem to have been a release in about a year, whereas point releases would previously come along once every couple of months.
Thanks,
- Chris.
On Thu, Apr 7, 2011 at 8:17 AM, Chris Ball cjb@laptop.org wrote:
Hi David,
On Thu, Apr 07 2011, David Gilbert wrote:
I'm curious; do we have any interaction with the autotest project
- it seems it's whole point is automated kernel testing,.
http://autotest.kernel.org/ and test.kernel.org
test.kernel.org hasn't done anything since around 2.6.36 -- I think it was run by Martin Bligh (one of the autotest authors) when he worked at Google, but he's not there anymore and isn't working on autotest now.
There's a similar question as to whether autotest itself is still being developed. It does at least have some large industry users sending in patches, but there doesn't seem to have been a release in about a year, whereas point releases would previously come along once every couple of months.
It is still being developed, but it seems that the major focus is on qemu.
That said, I use an autotest instance here in my own lab which has worked quite well for me for working with embedded boards.
g.
On Thu, Apr 21, 2011 at 10:41 AM, Grant Likely grant.likely@secretlab.ca wrote:
On Thu, Apr 7, 2011 at 8:17 AM, Chris Ball cjb@laptop.org wrote:
Hi David,
On Thu, Apr 07 2011, David Gilbert wrote:
I'm curious; do we have any interaction with the autotest project
- it seems it's whole point is automated kernel testing,.
http://autotest.kernel.org/ and test.kernel.org
test.kernel.org hasn't done anything since around 2.6.36 -- I think it was run by Martin Bligh (one of the autotest authors) when he worked at Google, but he's not there anymore and isn't working on autotest now.
There's a similar question as to whether autotest itself is still being developed. It does at least have some large industry users sending in patches, but there doesn't seem to have been a release in about a year, whereas point releases would previously come along once every couple of months.
It is still being developed, but it seems that the major focus is on qemu.
s/qemu/virtualization/
g.
-
Chris Ball -
David Gilbert -
Grant Likely -
Paul Larson