All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] new LTP testrunner
Date: Tue, 17 Jul 2018 16:45:55 +0200	[thread overview]
Message-ID: <20180717144555.GA22013@rei> (raw)
In-Reply-To: <1174539544.33712886.1531838009077.JavaMail.zimbra@redhat.com>

Hi!
> - replacing runltp + ltp-pan
> What I'm missing is the local use-case we have now. Something
> like backend:local, that will run the test on local system
> and produce same format of results. ssh into localhost
> adds complexity - some test wrapper might not know the
> password for system it has been spawned on.

It's there but not in the README, there is a sh backend that just runs
the tests in a localy executed shell see --help.

But I would like to discourage running the testcases locally for any
test automation/CI.

> The way we coped with (fatal) issues is pre-processing
> runtest files based on kernel version, package versions,
> architecture, etc.

This is something I wanted to avoid if possible because it requires to
maintain a database which time consuming and prone to errors.

> IMO backend:local (and ssh) might be closest to what people do now.
>
> - RFE: filter tests
> have ability to run only some tests based on some filter
> which is very common question I get about runltp

Yes, this is missing, but easy to add.

> - RFE: skip build/installation
> for some cross-compiling users
>   
> - "All backends needs to be able to reach internet"
> Why is this needed?

Just because the tool is expected to install LTP from GitHub.

But in the latest version if there is /opt/ltp/ already present on the
target machine it's not reinstalled unless you request it.

As I said it's still in a proof-of-concept state...

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2018-07-17 14:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 11:43 [LTP] [RFC] new LTP testrunner Cyril Hrubis
2018-07-17 14:33 ` Jan Stancek
2018-07-17 14:45   ` Cyril Hrubis [this message]
2018-07-17 15:28     ` Jan Stancek
2018-07-17 15:37       ` Cyril Hrubis
2018-07-18  1:27   ` [Fuego] " Daniel Sangorrin
2018-07-18  1:27     ` Daniel Sangorrin
2018-07-18  8:52     ` [Fuego] " Cyril Hrubis
2018-07-18  8:52       ` Cyril Hrubis

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=20180717144555.GA22013@rei \
    --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 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.