From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/1] Fix IGT runner error logic when listing subtests
Date: Mon, 20 Feb 2023 10:20:04 +0100 [thread overview]
Message-ID: <20230220092005.890959-1-mauro.chehab@linux.intel.com> (raw)
From: Mauro Carvalho Chehab <mchehab@kernel.org>
Patches may end breaking --list-subtests if they, for instance, have a
pattern like:
igt_fixture
fd = drm_open_driver(DRIVER);
...
do_something(fd);
igt_subtest("foo")
...
igt_subtest("bar")
...
As any usage of (fd) will cause a crash. As result, currently IGT
will produce stderror outbut, but will keep executing, producing
a wrong testlist, as "foo" and "bar" won't be listed.
That will also break scripts that would depend on a reliable testlist.
So, return an error on such cases.
Mauro Carvalho Chehab (1):
runner/job_list: return error on crashes while running --list-subtests
runner/job_list.c | 1 +
1 file changed, 1 insertion(+)
--
2.39.0
next reply other threads:[~2023-02-20 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 9:20 Mauro Carvalho Chehab [this message]
2023-02-20 9:20 ` [igt-dev] [PATCH i-g-t 1/1] runner/job_list: return error on crashes while running --list-subtests Mauro Carvalho Chehab
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=20230220092005.890959-1-mauro.chehab@linux.intel.com \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.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