From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Autotest mailing list <autotest@test.kernel.org>
Cc: KVM mailing list <kvm@vger.kernel.org>
Subject: [KVM-AUTOTEST PATCH 0/4] kvm test: fixing the 'autotest' subtest
Date: Fri, 12 Jun 2009 13:12:38 -0300 [thread overview]
Message-ID: <1244823158.2822.6.camel@localhost.localdomain> (raw)
The 'autotest' subtest of KVM got broke during the merge, since the new
logging system introduces new line prefixes on the autotest output. This
patch series fixes this subtest. It consists on:
* Fix a a few bad long line breaks
* Make the results parsing based on the status files of the autotest
job instead of stdout output
* Instead of relying on the sample control files that lie on the
autotest test directories, use our own directory with control files,
that will give us additional flexibility in editing and customizing the
control files that will run on guests
--
Lucas Meneghel Rodrigues
Software Engineer (QE)
Red Hat - Emerging Technologies
next reply other threads:[~2009-06-12 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 16:12 Lucas Meneghel Rodrigues [this message]
2009-06-15 21:36 ` [Autotest] [KVM-AUTOTEST PATCH 0/4] kvm test: fixing the 'autotest' subtest Lucas Meneghel Rodrigues
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1244823158.2822.6.camel@localhost.localdomain \
--to=lmr@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox