On 02/24/2012 07:50 PM, Lucas Meneghel Rodrigues wrote:
On 02/23/2012 12:27 PM, Guannan Ren wrote:
Hi Lucas,
Thanks for your these good modifications.
There is one place I noticed where you output each testcase of *.t
into a separate file with .tap extension.
hence, it has a corresponding log
On 02/23/2012 12:27 PM, Guannan Ren wrote:
Hi Lucas,
Thanks for your these good modifications.
There is one place I noticed where you output each testcase of *.t
into a separate file with .tap extension.
hence, it has a corresponding log file with little content for each
testcase. it seem a
Hi Lucas,
Thanks for your these good modifications.
There is one place I noticed where you output each testcase of
*.t into a separate file with .tap extension.
hence, it has a corresponding log file with little content for
each testcase. it seem a little harder
On Wed, Feb 22, 2012 at 06:45:58PM -0200, Lucas Meneghel Rodrigues wrote:
* Instead of making all tests output to the same DEBUG log, make
them output to separate .tap files on the results directory
So, the current output of the tests is like this:
$ sudo client/bin/autotest run libvirt_tck
On 02/23/2012 11:08 PM, Daniel P. Berrange wrote:
On Wed, Feb 22, 2012 at 06:45:58PM -0200, Lucas Meneghel Rodrigues wrote:
* Instead of making all tests output to the same DEBUG log, make
them output to separate .tap files on the results directory
So, the current output of the tests is like
Hi guys,
I was here looking at the autotest wrapper for libvirt TCK and then
decided to work on it, as I had the review fresh on my mind. Things that
I've worked on:
* Fixed some download links, that were already sent to upstream tck and
applied (thanks Dan Berrange)
* Instead of making all
