From: Riana Tauro <riana.tauro@intel.com>
To: "Gupta, Anshuman" <anshuman.gupta@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Nilawar, Badal" <badal.nilawar@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 0/2] Add GT id to identify failures
Date: Tue, 5 Sep 2023 12:21:35 +0530 [thread overview]
Message-ID: <898e839e-50e0-1725-cf6d-f567b243b3fc@intel.com> (raw)
In-Reply-To: <CY5PR11MB6211861228CB959139EA8EC095E8A@CY5PR11MB6211.namprd11.prod.outlook.com>
On 9/5/2023 11:46 AM, Gupta, Anshuman wrote:
>
>
>> -----Original Message-----
>> From: Tauro, Riana <riana.tauro@intel.com>
>> Sent: Tuesday, September 5, 2023 10:51 AM
>> To: igt-dev@lists.freedesktop.org
>> Cc: Tauro, Riana <riana.tauro@intel.com>; Gupta, Anshuman
>> <anshuman.gupta@intel.com>; Nilawar, Badal <badal.nilawar@intel.com>;
>> Sundaresan, Sujaritha <sujaritha.sundaresan@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
>
next prev parent reply other threads:[~2023-09-05 6:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 5:20 [igt-dev] [PATCH i-g-t 0/2] Add GT id to identify failures Riana Tauro
2023-09-05 5:20 ` [igt-dev] [PATCH i-g-t 1/2] tests/xe: Add GT id to C6 assertions Riana Tauro
2023-09-05 7:40 ` Sundaresan, Sujaritha
2023-09-05 5:20 ` [igt-dev] [PATCH i-g-t 2/2] tests/xe: Add GT id to identify failures Riana Tauro
2023-09-05 7:41 ` Sundaresan, Sujaritha
2023-09-05 5:44 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-09-05 6:16 ` [igt-dev] [PATCH i-g-t 0/2] " Gupta, Anshuman
2023-09-05 6:51 ` Riana Tauro [this message]
2023-09-05 6:54 ` Gupta, Anshuman
2023-09-05 6:16 ` [igt-dev] ✗ CI.xeBAT: failure for " Patchwork
2023-09-05 10:56 ` Tauro, Riana
2023-09-06 7:56 ` Yedireswarapu, SaiX Nandan
2023-09-05 6:25 ` [igt-dev] ✗ Fi.CI.BAT: " Patchwork
2023-09-06 7:36 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-09-06 10:10 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=898e839e-50e0-1725-cf6d-f567b243b3fc@intel.com \
--to=riana.tauro@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@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