Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: "Kamil Konieczny" <kamil.konieczny@linux.intel.com>,
	"vitaly prosyak" <vprosyak@amd.com>,
	"Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
	vitaly.prosyak@amd.com, igt-dev@lists.freedesktop.org,
	"Christian Koenig" <christian.koenig@amd.com>,
	"Alexander Deucher" <alexander.deucher@amd.com>,
	"Jesse Zhang" <jesse.zhang@amd.com>,
	"Harry Wentland" <harry.wentland@amd.com>
Subject: Re: [PATCH] lib/amd: add memleak functions
Date: Thu, 27 Feb 2025 12:13:10 +0100	[thread overview]
Message-ID: <b73547d3-0190-466c-84c2-d620842a653c@linux.intel.com> (raw)
In-Reply-To: <20250227105314.uuyemk5zhnjonr7r@kamilkon-desk.igk.intel.com>

Hi Kamil,

[...]

>>>
>>> sudo ./scripts/run-tests.sh -t -v /home/vprosyak/src/igt-gpu-tools/build/tests/amd/amd_basic
>>
>> I'm assuming this script calls igt_runner. If so, please add -keach as an
>> additional command-line argument to igt_runner.
>>
> 
> This is igt script and you can find it in igt sources.
> One way would be to extend it to accept -k option,
> the other to extend igtrc reading in runner/resume.
> Or both.

I was slow to understand that. But then I sent another
revision of the series to expand scripts/run-tests.sh
to support -K, as -k was already taken. You can see it
here:

https://patchwork.freedesktop.org/series/143996/

Thanks!

  reply	other threads:[~2025-02-27 11:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 11:43 [PATCH] lib/amd: add memleak functions vitaly.prosyak
2025-02-18 13:15 ` ✓ i915.CI.BAT: success for " Patchwork
2025-02-18 14:16 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-18 18:10 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-19  1:16 ` [PATCH] " Zhang, Jesse(Jie)
2025-02-19  4:49 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-02-19 10:41 ` [PATCH] " Kamil Konieczny
2025-02-19 17:50   ` vitaly prosyak
2025-02-26  9:09     ` Zbigniew Kempczyński
2025-02-26  9:43       ` Peter Senna Tschudin
2025-02-26 10:09         ` Zbigniew Kempczyński
2025-02-26 10:24           ` Peter Senna Tschudin
2025-02-27  5:08             ` vitaly prosyak
2025-02-27  9:08               ` Peter Senna Tschudin
2025-02-27 10:53                 ` Kamil Konieczny
2025-02-27 11:13                   ` Peter Senna Tschudin [this message]
2025-02-28  3:01                 ` vitaly prosyak
2025-02-27 10:27               ` Peter Senna Tschudin
2025-02-28  3:17                 ` vitaly prosyak

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=b73547d3-0190-466c-84c2-d620842a653c@linux.intel.com \
    --to=peter.senna@linux.intel.com \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=harry.wentland@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jesse.zhang@amd.com \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=vitaly.prosyak@amd.com \
    --cc=vprosyak@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