From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v5 2/3] Add LVM support scripts
Date: Tue, 14 Apr 2020 16:08:32 +0200 [thread overview]
Message-ID: <20200414140832.GC6700@yuki.lan> (raw)
In-Reply-To: <1a9956bc-f6b8-f360-e8c8-14fa59bee91b@suse.cz>
Hi!
> >> generate_lvm_runfile.sh will be called near the end of install_ltp to
> >> generate system-specific runfile for LVM tests using the template.
> >> prepare_lvm.sh will be called in a separate OpenQA module right after
> >> boot_ltp. None of these helper scripts should be included in any runfile.
> >
> > So these are OpenQA specific scripts, I do not think that they belong to
> > LTP upstream unless we make then work with upstream LTP.
>
> These scripts have no dependencies on OpenQA and can be used to prepare
> LVM test environment under any harness, including manual testing. I've
> made some design choices to ensure compatibility with OpenQA but they're
> really meant as full replacement for testscripts/ltpfslvm.sh which has
> been in LTP since forever.
Sure but unless there is a glue script that actually makes the tests run
or at least a README it's kind of pointless.
I would really prefer if there was something that coulud execute these
tests in upstream by starting a single script, so that it's clear how
these script should be used in the first place.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-04-14 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 8:59 [LTP] [PATCH v5 1/3] Allow acquiring multiple loop devices Martin Doucha
2020-04-14 8:59 ` [LTP] [PATCH v5 2/3] Add LVM support scripts Martin Doucha
2020-04-14 12:29 ` Cyril Hrubis
2020-04-14 13:02 ` Martin Doucha
2020-04-14 13:05 ` Cyril Hrubis
2020-04-14 13:49 ` Martin Doucha
2020-04-14 14:08 ` Cyril Hrubis [this message]
2020-04-14 8:59 ` [LTP] [PATCH v5 3/3] Skip Btrfs in LVM stress tests Martin Doucha
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=20200414140832.GC6700@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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