From: SeongJae Park <sj38.park@gmail.com>
To: shuah@kernel.org, brendanhiggins@google.com
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH] kunit: Fix '--build_dir' option
Date: Fri, 6 Sep 2019 21:05:41 +0900 [thread overview]
Message-ID: <1567771541-7690-1-git-send-email-sj38.park@gmail.com> (raw)
kunit fails to run with '--build_dir' option because the option is not
properly sent to kernel running procedure. This commit fixes the
problem.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
tools/testing/kunit/kunit.py | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tools/testing/kunit/kunit.py b/tools/testing/kunit/kunit.py
index 8d33980..e016430 100755
--- a/tools/testing/kunit/kunit.py
+++ b/tools/testing/kunit/kunit.py
@@ -62,9 +62,11 @@ def run_tests(linux: kunit_kernel.LinuxSourceTree,
'Tests not Parsed.')
if request.raw_output:
kunit_parser.raw_output(
- linux.run_kernel(timeout=request.timeout))
+ linux.run_kernel(timeout=request.timeout,
+ build_dir=request.build_dir))
else:
- kunit_output = linux.run_kernel(timeout=request.timeout)
+ kunit_output = linux.run_kernel(timeout=request.timeout,
+ build_dir=request.build_dir)
test_result = kunit_parser.parse_run_tests(kunit_output)
test_end = time.time()
--
2.7.4
next reply other threads:[~2019-09-06 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 12:05 SeongJae Park [this message]
2019-09-06 15:51 ` [PATCH] kunit: Fix '--build_dir' option shuah
2019-09-06 16:11 ` SeongJae Park
2019-09-06 16:11 ` SeongJae Park
2019-09-07 1:16 ` Brendan Higgins
2019-09-07 2:33 ` shuah
2019-09-07 9:08 ` SeongJae Park
2019-10-07 22:03 ` Brendan Higgins
2019-10-07 23:05 ` shuah
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=1567771541-7690-1-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=brendanhiggins@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.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;
as well as URLs for NNTP newsgroup(s).