All of lore.kernel.org
 help / color / mirror / Atom feed
From: =?unknown-8bit?q?Myl=C3=A8ne?= Josserand <mylene.josserand@bootlin.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] commands: Remove all test cases
Date: Tue, 29 May 2018 17:13:19 +0200	[thread overview]
Message-ID: <20180529171319.365ca9c0@dell-desktop.home> (raw)
In-Reply-To: <20180516101251.trwf4pxvqbqkqmp5@dell5510>

Hello,

On Wed, 16 May 2018 12:12:51 +0200
Petr Vorel <pvorel@suse.cz> wrote:

> Hi,
> 
> > > I guess most of user space tools not related to kernel (cp, cron, df, ln, tar, unzip, wc,
> > > which) are questionable.  
> 
> > It's really hard to draw a line here, but I would probably vote for
> > keeping tests that are working with files such as cp/df/ln as these
> > are basically just printing result from UNIX/POSIX syscalls.  
> 
> > We probably want to get rid of the unzip and wc test, since that is not
> > really kernel related.  
> 
> I recently pushed some patches sent by Mylène Josserand, just in case we don't get rid of
> these tests.

Yes, thank you for that!

> 
> BTW Mylène, Thomas, do you know people running these test on embedded? That might justify
> some of the tests (not sure if it's possible to run busybox tests without compilation -
> for machines which have their sources cross compiled).

We currently have one customer that run these tests on an embedded
platform but in fact, we run the default scenario_group (that is why,
we run "commands" runtest). I guess that if the community think these
tests are not useful anymore, there is no problem on our side.
Our customer is using it to "show" that LTP is successfully runnable on
their platform, that it is.

I am pretty new to LTP but I had the feeling that these "commands"
tests rely maybe too much on applications and not on Linux kernel
features. Many of them are returning TCONF in our case because we do
not have the correct configuration (busybox options, etc).

Thank you in advance,

Best regards,

-- 
Mylène Josserand, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

  parent reply	other threads:[~2018-05-29 15:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 13:24 [LTP] Commands test cases Sebastian Chlad
2018-04-26 13:24 ` [LTP] [PATCH] commands: Remove all " Sebastian Chlad
2018-04-26 13:47   ` Petr Vorel
2018-04-26 14:48     ` Sebastian Chlad
2018-04-27  2:59     ` Li Wang
2018-04-26 14:28   ` Alexey Kodanev
2018-04-26 14:49     ` Sebastian Chlad
2018-04-27  7:20       ` Jan Stancek
2018-04-27  7:41         ` Li Wang
2018-04-26 17:27     ` Petr Vorel
2018-04-27  0:35       ` Xiao Yang
2018-04-27  0:35       ` Xiao Yang
2018-04-27  7:02         ` Petr Vorel
2018-04-27 11:35       ` Cyril Hrubis
2018-04-27 11:37         ` Cyril Hrubis
2018-05-16 10:12         ` Petr Vorel
2018-05-25 14:36           ` Sebastian Chlad
2018-05-29 15:13           ` =?unknown-8bit?q?Myl=C3=A8ne?= Josserand [this message]
2018-05-30  9:31             ` Cyril Hrubis
2018-06-04  6:34             ` 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=20180529171319.365ca9c0@dell-desktop.home \
    --to=mylene.josserand@bootlin.com \
    --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.