From: Michael Goldish <mgoldish@redhat.com>
To: autotest@test.kernel.org, kvm@vger.kernel.org
Cc: Michael Goldish <mgoldish@redhat.com>
Subject: [KVM-AUTOTEST PATCH] KVM test: deal with incompatible env files gracefully (using version numbers)
Date: Wed, 7 Jul 2010 13:32:18 +0300 [thread overview]
Message-ID: <1278498738-2622-3-git-send-email-mgoldish@redhat.com> (raw)
In-Reply-To: <1278498738-2622-2-git-send-email-mgoldish@redhat.com>
Keep a version number in kvm.py (env_version) and record it in new env objects.
When loading an env file, compare its version against env_version. If it's too
old, don't use it.
When changes are made to the KVM test that break compatibility with existing
env files, env_version should be increased.
This will prevent exceptions being raised due to newly added VM attributes that
are missing from old env files.
Signed-off-by: Michael Goldish <mgoldish@redhat.com>
---
client/tests/kvm/kvm.py | 3 ++-
client/tests/kvm/kvm_utils.py | 16 +++++++++++-----
2 files changed, 13 insertions(+), 6 deletions(-)
diff --git a/client/tests/kvm/kvm.py b/client/tests/kvm/kvm.py
index 9da4c33..f656238 100644
--- a/client/tests/kvm/kvm.py
+++ b/client/tests/kvm/kvm.py
@@ -21,6 +21,7 @@ class kvm(test.test):
(Online doc - Getting started with KVM testing)
"""
version = 1
+ env_version = 0
def run_once(self, params):
# Report the parameters we've received and write them as keyvals
@@ -39,7 +40,7 @@ class kvm(test.test):
logging.info("Unpickling env. You may see some harmless error "
"messages.")
env_filename = os.path.join(self.bindir, params.get("env", "env"))
- env = kvm_utils.load_env(env_filename, {})
+ env = kvm_utils.load_env(env_filename, self.env_version)
logging.debug("Contents of environment: %s", env)
test_passed = False
diff --git a/client/tests/kvm/kvm_utils.py b/client/tests/kvm/kvm_utils.py
index 4183f1c..fb2d1c2 100644
--- a/client/tests/kvm/kvm_utils.py
+++ b/client/tests/kvm/kvm_utils.py
@@ -21,17 +21,23 @@ def dump_env(obj, filename):
file.close()
-def load_env(filename, default={}):
+def load_env(filename, version):
"""
- Load KVM test environment from an environment file.
+ Load KVM test environment from an env file.
+ If the version recorded in the file is lower than version, return an empty
+ env. If some other error occurs during unpickling, return an empty env.
- @param filename: Path to a file where the environment was dumped to.
+ @param filename: Path to an env file.
"""
+ default = {"version": version}
try:
file = open(filename, "r")
- obj = cPickle.load(file)
+ env = cPickle.load(file)
file.close()
- return obj
+ if env.get("version", 0) < version:
+ logging.warn("Incompatible env file found. Not using it.")
+ return default
+ return env
# Almost any exception can be raised during unpickling, so let's catch
# them all
except Exception, e:
--
1.5.4.1
next prev parent reply other threads:[~2010-07-07 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 10:32 [KVM-AUTOTEST PATCH] KVM test: kvm_vm.py: do not check nic_mode when adding -tftp option Michael Goldish
2010-07-07 10:32 ` [KVM-AUTOTEST PATCH] KVM test: rss.cpp: minimize window by default so it doesn't bother step files Michael Goldish
2010-07-07 10:32 ` Michael Goldish [this message]
2010-07-08 1:43 ` [Autotest] " Chen Cao
2010-07-08 10:23 ` Michael Goldish
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=1278498738-2622-3-git-send-email-mgoldish@redhat.com \
--to=mgoldish@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).