From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Swati Sharma <swati2.sharma@intel.com>,
igt-dev@lists.freedesktop.org, zbigniew.kempczynski@intel.com,
Vitaly Prosyak <vitaly.prosyak@amd.com>
Subject: Re: [PATCH i-g-t] lib/igt_core: Distinguish dynamic subtest in finished messages
Date: Thu, 11 Jun 2026 10:42:31 +0200 [thread overview]
Message-ID: <cf3517458599630f209ddd247d8183bb74f509e1.camel@linux.intel.com> (raw)
In-Reply-To: <20260610152928.yauflzchk2uf7szw@kamilkon-DESK.igk.intel.com>
On Wed, 2026-06-10 at 17:29 +0200, Kamil Konieczny wrote:
> Hi Swati,
> On 2026-06-09 at 01:08:07 +0530, Swati Sharma wrote:
> > The exit_subtest() function always printed 'finished subtest' in kmsg
> > and trace output regardless of whether it was a regular subtest or a
> > dynamic subtest finishing. The 'starting' messages already correctly
> > distinguish between the two ('starting subtest' vs 'starting dynamic
> > subtest').
> >
> > Fix the 'finished' messages to print 'finished dynamic subtest' for
> > dynamic subtests, matching the starting message convention. This makes
> > syslog parsing and test hang detection more accurate.
>
> Should you add Closes tag here? See
> https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/work_items/198
> Fix multiple results from one (dynamic) subtest reported
>
> +cc Janusz
> Cc: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
>
> >
> > Assisted-by: GitHub Copilot:Claude Opus 4.6
> > Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> > ---
> > lib/igt_core.c | 10 ++++++----
> > 1 file changed, 6 insertions(+), 4 deletions(-)
>
> This could potentailly affect other CI pipelines, so
> +cc Vitaly.
>
> Regards,
> Kamil
>
> >
> > diff --git a/lib/igt_core.c b/lib/igt_core.c
> > index dc3ac5304..a0d9c9d7d 100644
> > --- a/lib/igt_core.c
> > +++ b/lib/igt_core.c
> > @@ -1733,10 +1733,12 @@ __noreturn static void exit_subtest(const char *result)
> > *subtest_name,
> > result,
> > igt_time_elapsed(thentime, &now));
> > - igt_kmsg(KMSG_INFO "%s: finished subtest %s, %s\n",
> > - command_str, *subtest_name, result);
> > - igt_trace("%s: finished subtest %s, %s\n",
> > - command_str, *subtest_name, result);
> > + igt_kmsg(KMSG_INFO "%s: finished %s %s, %s\n",
> > + command_str, in_dynamic_subtest ? "dynamic subtest" : "subtest",
> > + *subtest_name, result);
> > + igt_trace("%s: finished %s %s, %s\n",
> > + command_str, in_dynamic_subtest ? "dynamic subtest" : "subtest",
> > + *subtest_name, result);
Isn't igt_runner watching those messages? Won't it be confused if not
adjusted to the new message content?
Thanks,
Janusz
> >
> > igt_terminate_spins();
> >
> > --
> > 2.25.1
> >
prev parent reply other threads:[~2026-06-11 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 19:38 [PATCH i-g-t] lib/igt_core: Distinguish dynamic subtest in finished messages Swati Sharma
2026-06-09 0:43 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-06-09 0:50 ` ✓ i915.CI.BAT: " Patchwork
2026-06-09 6:32 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-09 9:48 ` [PATCH i-g-t] " Samala, Pranay
2026-06-09 10:03 ` ✗ i915.CI.Full: failure for " Patchwork
2026-06-10 15:29 ` [PATCH i-g-t] " Kamil Konieczny
2026-06-10 15:53 ` vitaly prosyak
2026-06-10 22:53 ` Alex Hung
2026-06-11 8:42 ` Janusz Krzysztofik [this message]
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=cf3517458599630f209ddd247d8183bb74f509e1.camel@linux.intel.com \
--to=janusz.krzysztofik@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=swati2.sharma@intel.com \
--cc=vitaly.prosyak@amd.com \
--cc=zbigniew.kempczynski@intel.com \
/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