From: shuah <shuah@kernel.org>
To: Heidi Fahim <heidifahim@google.com>,
brendanhiggins@google.com, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org
Cc: frowand.list@gmail.com, shuah <shuah@kernel.org>
Subject: Re: [PATCH v2] kunit: run kunit_tool from any directory
Date: Wed, 19 Feb 2020 15:18:08 -0700 [thread overview]
Message-ID: <be2a28e9-6e5b-37a7-b298-2fef410d3be3@kernel.org> (raw)
In-Reply-To: <20200218221916.239951-1-heidifahim@google.com>
Hi Heidi,
On 2/18/20 3:19 PM, Heidi Fahim wrote:
> Implemented small fix so that the script changes work directories to the
> root of the linux kernel source tree from which kunit.py is run. This
> enables the user to run kunit from any working directory. Originally
> considered using os.path.join but this is more error prone as we would
> have to find all file path usages and modify them accordingly. Using
> os.chdir ensures that the entire script is run within /linux.
>
> Signed-off-by: Heidi Fahim <heidifahim@google.com>
> Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Thanks for the patch. In the future please include changes from v1
to v2.
I am assuming this v2 addresses Frank's comments.
> ---
> tools/testing/kunit/kunit.py | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/tools/testing/kunit/kunit.py b/tools/testing/kunit/kunit.py
> index 3f552e847a14..060d960a7029 100755
> --- a/tools/testing/kunit/kunit.py
> +++ b/tools/testing/kunit/kunit.py
> @@ -26,6 +26,8 @@ KunitResult = namedtuple('KunitResult', ['status','result'])
> KunitRequest = namedtuple('KunitRequest', ['raw_output','timeout', 'jobs',
> 'build_dir', 'defconfig', 'json'])
>
> +KernelDirectoryPath = sys.argv[0].split('tools/testing/kunit/')[0]
> +
> class KunitStatus(Enum):
> SUCCESS = auto()
> CONFIG_FAILURE = auto()
> @@ -37,6 +39,13 @@ def create_default_kunitconfig():
> shutil.copyfile('arch/um/configs/kunit_defconfig',
> kunit_kernel.kunitconfig_path)
>
> +def get_kernel_root_path():
> + parts = sys.argv[0] if not __file__ else __file__
> + parts = os.path.realpath(parts).split('tools/testing/kunit')
> + if len(parts) != 2:
> + sys.exit(1)
> + return parts[0]
> +
> def run_tests(linux: kunit_kernel.LinuxSourceTree,
> request: KunitRequest) -> KunitResult:
> config_start = time.time()
> @@ -130,6 +139,9 @@ def main(argv, linux=None):
> cli_args = parser.parse_args(argv)
>
> if cli_args.subcommand == 'run':
> + if get_kernel_root_path():
> + os.chdir(get_kernel_root_path())
> +
> if cli_args.build_dir:
> if not os.path.exists(cli_args.build_dir):
> os.mkdir(cli_args.build_dir)
>
thanks,
-- Shuah
next prev parent reply other threads:[~2020-02-19 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 22:19 Heidi Fahim
2020-02-19 22:18 ` shuah [this message]
[not found] ` <CAMVcs3uRj2uhFJXA+GEZmNjvNFF+3ODNmAON++scx26tnVhScA@mail.gmail.com>
2020-02-19 22:41 ` 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=be2a28e9-6e5b-37a7-b298-2fef410d3be3@kernel.org \
--to=shuah@kernel.org \
--cc=brendanhiggins@google.com \
--cc=frowand.list@gmail.com \
--cc=heidifahim@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.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
all inboxes | Powered by JetHome®