From: Shuah Khan <shuahkh@osg.samsung.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Cc: Dave Jones <davej@codemonkey.org.uk>, mmarek@suse.cz
Subject: Re: [PATCH 2/9] selftests: Add install target
Date: Tue, 10 Mar 2015 09:11:09 -0600 [thread overview]
Message-ID: <54FF098D.7020106@osg.samsung.com> (raw)
In-Reply-To: <54FE1EC0.6000201@osg.samsung.com>
On 03/09/2015 04:29 PM, Shuah Khan wrote:
> On 03/09/2015 08:20 AM, Shuah Khan wrote:
>> On 03/05/2015 11:53 AM, Dave Jones wrote:
>>> On Tue, Mar 03, 2015 at 03:51:35PM +1100, Michael Ellerman wrote:
>>> > This adds make install support to selftests. The basic usage is:
>>> >
>>> > $ cd tools/testing/selftests
>>> > $ make install
>>> >
>>> > That installs into tools/testing/selftests/install, which can then be
>>> > copied where ever necessary.
>>> >
>>> > The install destination is also configurable using eg:
>>> >
>>> > $ INSTALL_PATH=/mnt/selftests make install
>>>
>>> ...
>>>
>>> > + @# Ask all targets to emit their test scripts
>>> > + echo "#!/bin/bash\n\n" > $(ALL_SCRIPT)
>>>
>>> $ ./all.sh
>>> -bash: ./all.sh: /bin/bash\n\n: bad interpreter: No such file or directory
>>>
>>> Removing the \n\n fixes it.
>>>
>>> > + echo "cd \$$ROOT\n" >> $(ALL_SCRIPT); \
>>>
>>> ditto
>>>
>>> Dave
>>
>> Michael,
>>
>> Could you please fix these problems and send the patch.
>>
>
> Michael,
>
> Did you happen to run run_kselftest.sh from the install
> directory to make sure all the dependent executables
> are installed? You are missing a few required dependencies.
> efivars test for example.
>
> Please run kselftest_install.sh I sent out for review and
> compare the following:
>
> - contents of install directory created with your patch vs.
> my kselftest_install.sh tool
> - Compare your run_kselftest.sh run with the one that gets
> generated with my kselftest_install.sh tool
>
> General rule is all tests that get run when run_tests target
> is run should run from the install directory using the
> run_kselftest.sh generated during install.
>
Couple more things. Please change the install directory name
to kselftest
tools/testing/selftests/kselftest
instead of
tools/testing/selftests/install
Also please flatten the directory structure under the install
directory. I don't see any value in creating directory for each
test for install. Also it is makes it cumbersome for users
to navigate and work with after the install. This would mean cpu
and memory hot-plug scripts need unique names.
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2015-03-10 15:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 4:51 [PATCH 1/9] selftests: Introduce minimal shared logic for running tests Michael Ellerman
2015-03-03 4:51 ` [PATCH 2/9] selftests: Add install target Michael Ellerman
2015-03-05 18:53 ` Dave Jones
2015-03-09 14:20 ` Shuah Khan
2015-03-09 22:29 ` Shuah Khan
2015-03-10 15:11 ` Shuah Khan [this message]
2015-03-11 3:20 ` Michael Ellerman
2015-03-11 13:19 ` Shuah Khan
2015-03-11 3:15 ` Michael Ellerman
2015-03-11 3:18 ` Dave Jones
2015-03-03 4:51 ` [PATCH 3/9] selftests: Add install support for the powerpc tests Michael Ellerman
2015-03-03 4:51 ` [PATCH 4/9] kbuild: add a new kselftest_install make target to install selftests Michael Ellerman
2015-03-03 4:51 ` [PATCH 5/9] kbuild: Don't pass -rR to selftest makefiles Michael Ellerman
2015-03-03 4:51 ` [PATCH 6/9] selftests: Set CC using CROSS_COMPILE once in lib.mk Michael Ellerman
2015-03-03 4:51 ` [PATCH 7/9] selftests/timers: Use implicit rules Michael Ellerman
2015-03-03 4:51 ` [PATCH 8/9] selftests/mqueue: " Michael Ellerman
2015-03-03 4:51 ` [PATCH 9/9] selftests/mount: " Michael Ellerman
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=54FF098D.7020106@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=mpe@ellerman.id.au \
/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