public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: autotest@test.kernel.org
Cc: kvm@vger.kernel.org, Lucas Meneghel Rodrigues <lmr@redhat.com>
Subject: [PATCH] KVM test: Fixing kvm release tag detection
Date: Sun,  5 Jul 2009 21:57:48 -0300	[thread overview]
Message-ID: <1246841868-6654-1-git-send-email-lmr@redhat.com> (raw)

The recent sourceforge facelift/changes broke our ability to determine
KVM release tags. This patch fixes up things.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
---
 client/tests/kvm/kvm_utils.py |    6 +-----
 1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/client/tests/kvm/kvm_utils.py b/client/tests/kvm/kvm_utils.py
index a37d322..b2b0d1a 100644
--- a/client/tests/kvm/kvm_utils.py
+++ b/client/tests/kvm/kvm_utils.py
@@ -139,13 +139,9 @@ def get_latest_kvm_release_tag(release_dir):
         f = open(local_web_page, "r")
         data = f.read()
         f.close()
-        rx = re.compile("package_id=(\d+).*\>kvm\<", re.IGNORECASE)
+        rx = re.compile("kvm-(\d+).tar.gz", re.IGNORECASE)
         matches = rx.findall(data)
         package_id = matches[0]
-        #package_id = 209008
-        rx = re.compile("package_id=%s.*release_id=\d+\">(\d+)" % package_id, 
-                        re.IGNORECASE)
-        matches = rx.findall(data)
         return matches[0] # the first match contains the latest release tag
     except Exception, e:
         message = "Could not fetch latest KVM release tag: %s" % str(e)
-- 
1.6.2.5


             reply	other threads:[~2009-07-06  0:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  0:57 Lucas Meneghel Rodrigues [this message]
2009-07-06 15:21 ` [PATCH] KVM test: Fixing kvm release tag detection 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=1246841868-6654-1-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