From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: autotest@test.kernel.org
Cc: kvm@vger.kernel.org
Subject: [PATCH 2/3] virt.virt_utils: Get rid of create_report function
Date: Thu, 28 Apr 2011 16:08:53 -0300 [thread overview]
Message-ID: <1304017734-15836-3-git-send-email-lmr@redhat.com> (raw)
In-Reply-To: <1304017734-15836-1-git-send-email-lmr@redhat.com>
As it has been transfered to the html_report module itself.
Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
---
client/virt/virt_utils.py | 12 ------------
1 files changed, 0 insertions(+), 12 deletions(-)
diff --git a/client/virt/virt_utils.py b/client/virt/virt_utils.py
index 97a652d..8fa64ca 100644
--- a/client/virt/virt_utils.py
+++ b/client/virt/virt_utils.py
@@ -1187,18 +1187,6 @@ def run_tests(parser, job):
return not failed
-def create_report(report_dir, results_dir):
- """
- Creates a neatly arranged HTML results report in the results dir.
-
- @param report_dir: Directory where the report script is located.
- @param results_dir: Directory where the results will be output.
- """
- reporter = os.path.join(report_dir, 'html_report.py')
- html_file = os.path.join(results_dir, 'results.html')
- os.system('%s -r %s -f %s -R' % (reporter, results_dir, html_file))
-
-
def display_attributes(instance):
"""
Inspects a given class instance attributes and displays them, convenient
--
1.7.4.4
next prev parent reply other threads:[~2011-04-28 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 19:08 [PATCH 0/3] Fix HTML report generation Lucas Meneghel Rodrigues
2011-04-28 19:08 ` [PATCH 1/3] tools/html_report: Make html report generation autotest generic Lucas Meneghel Rodrigues
2011-04-28 19:08 ` Lucas Meneghel Rodrigues [this message]
2011-04-28 19:08 ` [PATCH 3/3] KVM test: control: Replace create_report function call 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=1304017734-15836-3-git-send-email-lmr@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).