From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 ltp] runltp: fix shellcheck error for sending email
Date: Mon, 15 Oct 2018 21:16:31 +0200 [thread overview]
Message-ID: <20181015191631.GA26749@dell5510> (raw)
In-Reply-To: <20181015145126.GB28106@rei>
Hi,
> > It might be easier to get people using it if it were in tree. Would it
> > be possible to have runltp and runltp-ng both in tree? Until then, it's
> > hard to not support the only available runner.
> That is a fair point.
You're right. I pushed the commit (no matter the state of the code, bashisms
should be fixed).
> > Looking at the README at
> > https://github.com/metan-ucw/ltp/tree/master/tools/runltp-ng, it's hard
> > to tell if it has feature parity with runltp, or if there are still
> > gaps. Some example usecases would be nice too. For example, I see the
> > list of back ends, but what if I want to run it locally (today's
> > behavior)?
> And the lack of documentation and the fact that the code is not yet
> considered stable enough is the reason why it's not in-tree.
Sorry for pointing to runltp-ng, which might not be yet ready for using/testing.
I meant that more like info for users, not to waste time with something
which should have been either rewritten from scratch or replaced.
> I guess that the test-runner can be put into a separate git repo, it
> does not depend on the rest of the LTP in any way, which should make it
> easier to get the source code, without pulling in the outdated LTP
> repostitory.
> Also the local test execution is called shell backend, in that case the
> testrunner forks a shell instead of doing a ssh connection and executes
> the testcases locally.
I haven't looked into the code myself (planning to), but it's really promising :).
Kind regards,
Petr
next prev parent reply other threads:[~2018-10-15 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 8:34 [LTP] [PATCH v2 ltp] runltp: fix shellcheck error for sending email Yixin Zhang
2018-10-15 9:52 ` Petr Vorel
2018-10-15 11:19 ` Zhang, Yixin
2018-10-15 14:18 ` Dan Rue
2018-10-15 14:51 ` Cyril Hrubis
2018-10-15 19:16 ` Petr Vorel [this message]
2018-10-15 19:07 ` Petr Vorel
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=20181015191631.GA26749@dell5510 \
--to=pvorel@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.