Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: vitaly prosyak <vprosyak@amd.com>
To: "Jesse.zhang@amd.com" <jesse.zhang@amd.com>,
	igt-dev@lists.freedesktop.org
Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Christian Koenig <christian.koenig@amd.com>,
	Kamil Konieczny <kamil.konieczny@linux.intel.com>
Subject: Re: [PATCH i-g-t] tests/amd_queue_reset: fix dynamic subtest issue for amd queue reset
Date: Mon, 12 Aug 2024 21:03:52 -0400	[thread overview]
Message-ID: <6b7ab7e3-bfc5-4e7d-a8fd-9c025447832a@amd.com> (raw)
In-Reply-To: <20240812075051.2925305-1-jesse.zhang@amd.com>

The changed looks good to me.

Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>

On 2024-08-12 03:50, Jesse.zhang@amd.com wrote:
> Correct the usage of igt_dynamic_f or it always print SUCCESS, like this:
>
> Starting subtest: amdgpu-gfx-CMD_STREAM_EXEC_INVALID_OPCODE
> Starting dynamic subtest: amdgpu-CMD_STREAM_EXEC_INVALID_OPCODE-1
> Dynamic subtest amdgpu-CMD_STREAM_EXEC_INVALID_OPCODE-1: SUCCESS (0.000s)
>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Cc: Christian Koenig <christian.koenig@amd.com>
> Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>
>
> Signed-off-by: Jesse Zhang <jesse.zhang@amd.com>
> ---
>  tests/amdgpu/amd_queue_reset.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/tests/amdgpu/amd_queue_reset.c b/tests/amdgpu/amd_queue_reset.c
> index 1a128265a..729286d82 100644
> --- a/tests/amdgpu/amd_queue_reset.c
> +++ b/tests/amdgpu/amd_queue_reset.c
> @@ -1000,9 +1000,8 @@ igt_main
>  			igt_describe("Stressful-and-multiple-cs-of-bad and good length-operations-using-multiple-processes");
>  			igt_subtest_with_dynamic_f("amdgpu-%s-%s", ip_tests[i] == AMD_IP_COMPUTE ? "COMPUTE":"GRAPHIX", it->name) {
>  				if (arr_cap[ip_tests[i]] && get_next_rings(ring_id_good, info, &ring_id_good, &ring_id_bad, i)) {
> -					igt_dynamic_f("amdgpu-%s-ring-good-%d-bad-%d-%s", it->name,ring_id_good, ring_id_bad, ip_tests[i] == AMD_IP_COMPUTE ? "COMPUTE":"GRAPHIX");
> -					set_next_test_to_run(sh_mem, it->test,
> -							ip_background, ip_tests[i], ring_id_good, ring_id_bad);
> +					igt_dynamic_f("amdgpu-%s-ring-good-%d-bad-%d-%s", it->name,ring_id_good, ring_id_bad, ip_tests[i] == AMD_IP_COMPUTE ? "COMPUTE":"GRAPHIX")
> +					set_next_test_to_run(sh_mem, it->test, ip_background, ip_tests[i], ring_id_good, ring_id_bad);
>  				}
>  			}
>  		}

      parent reply	other threads:[~2024-08-13  1:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12  7:50 [PATCH i-g-t] tests/amd_queue_reset: fix dynamic subtest issue for amd queue reset Jesse.zhang@amd.com
2024-08-12 12:27 ` ✗ GitLab.Pipeline: warning for " Patchwork
2024-08-12 12:44 ` ✓ CI.xeBAT: success " Patchwork
2024-08-12 12:57 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-12 16:21 ` ✗ CI.xeFULL: failure " Patchwork
2024-08-12 23:43 ` ✗ Fi.CI.IGT: " Patchwork
2024-08-13  1:03 ` vitaly prosyak [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=6b7ab7e3-bfc5-4e7d-a8fd-9c025447832a@amd.com \
    --to=vprosyak@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jesse.zhang@amd.com \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=vitaly.prosyak@amd.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