Lucas Meneghel
Lucas Meneghel
We need a smart test runner that has: - Minimalistic logging - Runs arbitrary user space commands and analyze return codes for 'trivial' codes.
Some work was done by Wu Zhangjin [email protected] on cross compilation support: http://test.kernel.org/pipermail/autotest/2012-April/010240.html We need to: 0) Research prior art in the autotest tree 1) Pick up his initial control...
Using libvirt of anyhting that makes sense.
We want to be able to reduce the number of files a user is presented when looking autotest results.
Support for generating TAP report files is already in autotest, but there's still no parser for TAP result files, which will be useful to directly consume results produced by another...
So we can use the functionality programatically, say, by an RPC call or directly, by other consuming programs.
That will help people setting up an autotest packaging repo https://github.com/autotest/autotest/wiki/PackagingExample
Beaker (https://fedorahosted.org/beaker/) has a concept of a watchdog, that is, code that watches out to see if a given task completed in the specified amount of time. There are 2...
This is the list of virttest.virsh APIs used by libvirt_vm: ``` from virttest.virsh import command from virttest.virsh import attach_interface from virttest.virsh import canonical_uri from virttest.virsh import define from virttest.virsh import...
Although we don't need to do it in a hurry, I'd like to take a look in possible replacements for the aexpect code. Pros: 1) We won't have to maintain...