From: Avi Kivity <avi@redhat.com>
To: Mike Burns <mburns@redhat.com>
Cc: kvm@vger.kernel.org, dhuff@redhat.com, ulublin@redhat.com
Subject: Re: [PATCH][KVM-AUTOTEST] Have Custom install chdir to test.bindir
Date: Sun, 24 May 2009 17:51:01 +0300 [thread overview]
Message-ID: <4A195ED5.6030001@redhat.com> (raw)
In-Reply-To: <1242851931-8492-1-git-send-email-mburns@redhat.com>
Mike Burns wrote:
> If you are using custom install and load_modules=yes, then autotest needs to
> change to the test.bindir so that it looks for kernel modules in the right
> place.
>
> Signed-off-by: Mike Burns <mburns@redhat.com>
> ---
> client/tests/kvm_runtest_2/kvm_install.py | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/client/tests/kvm_runtest_2/kvm_install.py b/client/tests/kvm_runtest_2/kvm_install.py
> index d1aceb2..ebd8b7d 100755
> --- a/client/tests/kvm_runtest_2/kvm_install.py
> +++ b/client/tests/kvm_runtest_2/kvm_install.py
> @@ -79,6 +79,7 @@ def run_kvm_install(test, params, env):
>
> # install from custom script
> elif install_mode == "custom":
> + os.chdir(test.bindir)
> install_script = params.get("install_script")
> script = os.path.join(test.bindir,install_script)
> if not install_script:
>
Don't you need to chdir back afterwards?
Opportunity for a with statement.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-24 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 20:38 [PATCH][KVM-AUTOTEST] Have Custom install chdir to test.bindir Mike Burns
2009-05-20 20:38 ` [PATCH][KVM-AUTOTEST] Check exit status of custom install script and fail if script failed Mike Burns
2009-05-24 14:48 ` Avi Kivity
2009-05-28 6:25 ` Lucas Meneghel Rodrigues
2009-06-01 7:57 ` Avi Kivity
2009-06-01 18:22 ` Mike Burns
2009-05-24 14:51 ` Avi Kivity [this message]
2009-06-01 18:39 ` [PATCH][KVM-AUTOTEST] Have Custom install chdir to test.bindir Mike Burns
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=4A195ED5.6030001@redhat.com \
--to=avi@redhat.com \
--cc=dhuff@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mburns@redhat.com \
--cc=ulublin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.