[igt-dev] [PATCH i-g-t 0/2] Add GT id to identify failures
Riana Tauro
riana.tauro at intel.com
Tue Sep 5 06:51:35 UTC 2023
On 9/5/2023 11:46 AM, Gupta, Anshuman wrote:
>
>
>> -----Original Message-----
>> From: Tauro, Riana <riana.tauro at intel.com>
>> Sent: Tuesday, September 5, 2023 10:51 AM
>> To: igt-dev at lists.freedesktop.org
>> Cc: Tauro, Riana <riana.tauro at intel.com>; Gupta, Anshuman
>> <anshuman.gupta at intel.com>; Nilawar, Badal <badal.nilawar at intel.com>;
>> Sundaresan, Sujaritha <sujaritha.sundaresan at intel.com>
>> Subject: [PATCH i-g-t 0/2] Add GT id to identify failures
>>
>> Add GT id to test assertions to identify which gt is causing a failure
> How about adding a debug log to print gt name in xe_is_gt_in_c6() as well ?
> Thanks,
> Anshuman Gupta.
Hi Anshuman
I did try that. Since it's under igt_wait and called multiple times (10)
The log is printed every time the function is called.
For some tests which use a loop, it was a lot of
prints.
Thanks
Riana Tauro
>>
>> Riana Tauro (2):
>> tests/intel/xe_pm_residency: Add GT id to C6 assertions
>> tests/intel/xe_guc_pc: Add GT id to C6 assertions
>>
>> tests/intel/xe_guc_pc.c | 18 ++++++++++++------
>> tests/intel/xe_pm_residency.c | 8 ++++----
>> 2 files changed, 16 insertions(+), 10 deletions(-)
>>
>> --
>> 2.40.0
>
More information about the igt-dev
mailing list