From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Petri Latvala <petri.latvala@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH RFC 2/2] lib/igt_core: print card sysfs node at subtest results
Date: Thu, 29 Sep 2022 14:56:58 +0200 [thread overview]
Message-ID: <982260e9-6b9b-6209-a2d4-7345caf09fee@linux.intel.com> (raw)
In-Reply-To: <YzVuHIriXmCIbiVT@platvala-desk.ger.corp.intel.com>
On 9/29/22 12:06, Petri Latvala wrote:
> On Thu, Sep 29, 2022 at 10:21:36AM +0200, Mauro Carvalho Chehab wrote:
>> On Wed, 28 Sep 2022 18:26:50 +0200
>> Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
>>
>>> Hi Mauro,
>>>
>>> On 2022-09-28 at 12:43:20 +0300, Petri Latvala wrote:
>>>> On Wed, Sep 28, 2022 at 10:58:42AM +0200, Mauro Carvalho Chehab wrote:
>>>>> From: Mauro Carvalho Chehab <mchehab@kernel.org>
>>>>>
>>>>> This helps to identify what GPU failed on multi-GPU tests.
>>>> And completely breaks igt_runner when it tries to parse the result
>>>> logs.
>> Yes. That's btw one of the reasons why I submitted it as a RFC: depending
>> on how CI check IGT logs, it can break the test results there as well.
>>
>> Anyway, this is fixable.
>>
>> The point is, once we have multi-GPU tests, we need to have a way to
>> report what GPU failed.
> Imho it's best printed in __igt_fail_assert to get it close to the
> reason why the test is failing.
Yeah, it makes sense to have it there, but, IMO it should also be at the
result
output, as we could have a test that it skipped on some GPUs and/or fail on
some GPUs while passing on others.
Regards,
Mauro
prev parent reply other threads:[~2022-09-29 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 8:58 [igt-dev] [PATCH RFC 0/2] add sysfs node at subtest results when available Mauro Carvalho Chehab
2022-09-28 8:58 ` [igt-dev] [PATCH RFC 1/2] lib/igt_core: add a logic to store a GPU string Mauro Carvalho Chehab
2022-09-28 8:58 ` [igt-dev] [PATCH RFC 2/2] lib/igt_core: print card sysfs node at subtest results Mauro Carvalho Chehab
[not found] ` <YzQXFRYCk8Alj4zR@platvala-desk.ger.corp.intel.com>
[not found] ` <YzR1ypRVkKtVXt22@kamilkon-desk1>
2022-09-29 8:21 ` Mauro Carvalho Chehab
[not found] ` <YzVuHIriXmCIbiVT@platvala-desk.ger.corp.intel.com>
2022-09-29 12:56 ` Mauro Carvalho Chehab [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=982260e9-6b9b-6209-a2d4-7345caf09fee@linux.intel.com \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@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