Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Dmitry Vyukov <dvyukov@google.com>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	Anders Roxell <anders.roxell@linaro.org>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>, shuah <shuah@kernel.org>
Subject: Re: kselftest build broken?
Date: Thu, 13 Jun 2019 08:10:06 -0600	[thread overview]
Message-ID: <f0f9f016-6c1f-447b-1713-7e582aedf74c@kernel.org> (raw)
In-Reply-To: <CAEUSe791S6ODPZq4gcfbY=5kZ98ss2qNm0ks-oo0XLwFjsO=ag@mail.gmail.com>

On 6/12/19 3:12 PM, Daniel Díaz wrote:
> Hello!
> 
> On Wed, 12 Jun 2019 at 14:32, shuah <shuah@kernel.org> wrote:
>> On 6/12/19 12:29 PM, Dmitry Vyukov wrote:
> [...]
>>> 1. You suggested to install a bunch of packages. That helped to some
>>> degree. Is there a way to figure out what packages one needs to
>>> install to build the tests other than asking you?
>>
>> I have to go through discovery at times when new tests get added. I
>> consider this a part of being a open source developer figuring out
>> dependencies for compiling and running. I don't have a magic answer
>> for you and there is no way to make sure all dependencies will be
>> documented.
> 
> This is something we, as users of Kselftests, would very much like to
> see improved. We also go by trial-and-error finding out what is
> missing, but keeping up with the new tests or subsystems is often
> difficult and tend to remain broken (in usage) for some time, until we
> have the resources to look into that and fix it. The config fragments
> is an excellent example of how the test developers and the framework
> complement each other to make things work. Even documenting
> dependencies would go a long way, as a starting point, but I do
> believe that the test writers should do that and not the users go
> figure out what all is needed to run their tests.
> 
> Maybe a precheck() on the tests in order to ensure that the needed
> binaries are around?
> 

Right. Take a look at x86 test Makefile - it handles that. Tests can
handle these in their Makefile - not at run-time.

I will be happy to take patches similar to the checks x86 does. These
shouldn't fail the kselftest build and print out dependencies.

This way users can go install them.

> For what it's worth, this is the list of run-time dependencies package
> for OpenEmbedded: bash bc ethtool fuse-utils iproute2 iproute2-tc
> iputils-ping iputils-ping6 ncurses perl sudo python3-argparse
> python3-datetime python3-json python3-pprint python3-subprocess
> util-linux-uuidgen cpupower glibc-utils. We are probably missing a
> few.
> 

Sure see above.

thanks,
-- Shuah

  parent reply	other threads:[~2019-06-13 15:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 10:30 kselftest build broken? Dmitry Vyukov
2019-06-11 15:16 ` shuah
2019-06-11 16:03   ` Dmitry Vyukov
2019-06-11 19:20     ` shuah
2019-06-12  8:51       ` Dmitry Vyukov
2019-06-12  9:09         ` Dmitry Vyukov
2019-06-12  9:13           ` Dmitry Vyukov
2019-06-12  9:19             ` Dmitry Vyukov
2019-06-12 11:05               ` Dmitry Vyukov
2019-06-12 11:35                 ` Dmitry Vyukov
2019-06-12 16:44                   ` shuah
2019-06-12 18:29                     ` Dmitry Vyukov
2019-06-12 19:32                       ` shuah
2019-06-12 21:12                         ` Daniel Díaz
2019-06-13  8:55                           ` Naresh Kamboju
2019-06-13 14:10                           ` shuah [this message]
2019-06-13 14:21                           ` Dmitry Vyukov
2019-06-13 14:58                             ` Daniel Díaz
2019-06-13 16:37                               ` Dmitry Vyukov
2019-06-13 14:03                         ` Dmitry Vyukov

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=f0f9f016-6c1f-447b-1713-7e582aedf74c@kernel.org \
    --to=shuah@kernel.org \
    --cc=anders.roxell@linaro.org \
    --cc=daniel.diaz@linaro.org \
    --cc=dvyukov@google.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    /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