public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [KVM-AUTOTEST PATCH] kvm_runtest_2.py: use pickle instead of shelve when loading/saving env
Date: Thu, 28 May 2009 10:26:02 -0300	[thread overview]
Message-ID: <1243517162.2976.1050.camel@localhost.localdomain> (raw)
In-Reply-To: <de2b74cada241e816c81e7e28cf6b6460a56dce9.1243179847.git.mgoldish@redhat.com>

On Sun, 2009-05-24 at 18:46 +0300, Michael Goldish wrote:
> pickle allows more control over the load/save process. Specifically, it enables
> us to dump the contents of an object to disk without having to unpickle it.
> shelve, which uses pickle, seems to pickle and unpickle every time sync() is
> called. This is bad for classes that need to be unpickled only once per test
> (such a class will be introduced in a future patch).

Looks good to me.

> Signed-off-by: Michael Goldish <mgoldish@redhat.com>
> ---
>  client/tests/kvm_runtest_2/kvm_runtest_2.py |   29 ++++++++++++++++++++------
>  1 files changed, 22 insertions(+), 7 deletions(-)
> 
> diff --git a/client/tests/kvm_runtest_2/kvm_runtest_2.py b/client/tests/kvm_runtest_2/kvm_runtest_2.py
> index a69951b..5f7f6ad 100644
> --- a/client/tests/kvm_runtest_2/kvm_runtest_2.py
> +++ b/client/tests/kvm_runtest_2/kvm_runtest_2.py
> @@ -3,9 +3,9 @@
>  import sys
>  import os
>  import time
> -import shelve
>  import random
>  import resource
> +import cPickle
>  
>  from autotest_lib.client.bin import test
>  from autotest_lib.client.common_lib import error
> @@ -18,6 +18,22 @@ class test_routine:
>          self.routine = None
>  
> 
> +def dump_env(obj, filename):
> +    file = open(filename, "w")
> +    cPickle.dump(obj, file)
> +    file.close()
> +
> +
> +def load_env(filename, default=None):
> +    try:
> +        file = open(filename, "r")
> +    except:
> +        return default
> +    obj = cPickle.load(file)
> +    file.close()
> +    return obj
> +
> +
>  class kvm_runtest_2(test.test):
>      version = 1
>  
> @@ -65,7 +81,7 @@ class kvm_runtest_2(test.test):
>  
>          # Open the environment file
>          env_filename = os.path.join(self.bindir, params.get("env", "env"))
> -        env = shelve.open(env_filename, writeback=True)
> +        env = load_env(env_filename, {})
>          kvm_log.debug("Contents of environment: %s" % str(env))
>  
>          try:
> @@ -87,24 +103,23 @@ class kvm_runtest_2(test.test):
>  
>                  # Preprocess
>                  kvm_preprocessing.preprocess(self, params, env)
> -                env.sync()
> +                dump_env(env, env_filename)
>                  # Run the test function
>                  routine_obj.routine(self, params, env)
> -                env.sync()
> +                dump_env(env, env_filename)
>  
>              except Exception, e:
>                  kvm_log.error("Test failed: %s" % e)
>                  kvm_log.debug("Postprocessing on error...")
>                  kvm_preprocessing.postprocess_on_error(self, params, env)
> -                env.sync()
> +                dump_env(env, env_filename)
>                  raise
>  
>          finally:
>              # Postprocess
>              kvm_preprocessing.postprocess(self, params, env)
>              kvm_log.debug("Contents of environment: %s" % str(env))
> -            env.sync()
> -            env.close()
> +            dump_env(env, env_filename)
>  
>      def postprocess(self):
>          pass
-- 
Lucas Meneghel Rodrigues
Software Engineer (QE)
Red Hat - Emerging Technologies


      reply	other threads:[~2009-05-28 13:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 15:46 [KVM-AUTOTEST PATCH] RHEL-4.7 step files: fix the initial boot barriers Michael Goldish
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] RHEL-5.3 step files: fix initial boot barriers and an inconsistent dialog Michael Goldish
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] WinXP step files: add an optional barrier to deal with a closed start menu Michael Goldish
2009-05-24 19:31   ` sudhir kumar
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] stepeditor.py: get rid of some annoying keyboard shortcuts Michael Goldish
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] Use new function VM.get_name() to get the VM's name, instead of VM.name Michael Goldish
2009-05-28 13:06   ` Lucas Meneghel Rodrigues
2009-06-03  5:01     ` Michael Goldish
2009-06-03 23:26       ` Lucas Meneghel Rodrigues
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] VM.create(): always destroy() the VM before attempting to start it Michael Goldish
2009-05-28 14:17   ` Lucas Meneghel Rodrigues
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] kvm_vm.py: choose a monitor filename in the constructor instead of VM.create() Michael Goldish
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] kvm_vm.py: make sure the bulk of VM.create() is not executed in parallel Michael Goldish
2009-05-24 19:25   ` sudhir kumar
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] kvm_vm.py: add new function VM.clone() which returns a clone of the VM Michael Goldish
2009-05-25 12:01   ` Avi Kivity
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] kvm_utils.py: remote_login(): improve regular expression matching Michael Goldish
2009-05-24 18:59   ` sudhir kumar
2009-05-29  6:12   ` Lucas Meneghel Rodrigues
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] kvm_vm.py: add new VM parameter 'x11_display' that controls $DISPLAY Michael Goldish
2009-05-28 13:26   ` Lucas Meneghel Rodrigues
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] kvm_runtest_2.py: use environment filename specified by the 'env' parameter Michael Goldish
2009-05-24 19:03   ` sudhir kumar
2009-05-28 13:26   ` Lucas Meneghel Rodrigues
2009-05-24 15:46 ` [KVM-AUTOTEST PATCH] kvm_runtest_2.py: use pickle instead of shelve when loading/saving env Michael Goldish
2009-05-28 13:26   ` Lucas Meneghel Rodrigues [this message]

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=1243517162.2976.1050.camel@localhost.localdomain \
    --to=lmr@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mgoldish@redhat.com \
    /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