On Thu, Apr 21, 2011 at 10:41 AM, Grant Likely
wrote:
> On Thu, Apr 7, 2011 at 8:17 AM, Chris Ball 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
On Thu, Apr 7, 2011 at 8:17 AM, Chris Ball 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://aut
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
On Thu, Apr 7, 2011 at 3:24 AM, 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
I did some looking at it, but what we are t
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
___
linaro-dev mailing list
linaro-dev@lists.linar
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
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 rem
