From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for Some refactor, rewrite and fixes for OA tests
Date: Tue, 18 Feb 2025 10:38:11 -0800 [thread overview]
Message-ID: <Z7TTk8Raw5CxwwwD@orsosgc001> (raw)
In-Reply-To: <173969315217.2891932.116693029209058418@b555e5b46a47>
Hi Ashutosh,
On Sun, Feb 16, 2025 at 08:05:52AM +0000, Patchwork wrote:
> Patch Details
>
> Series: Some refactor, rewrite and fixes for OA tests
> URL: [1]https://patchwork.freedesktop.org/series/144916/
> State: failure
> Details: [2]https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12607/index.html
>
> CI Bug Log - changes from XEIGT_8230_full -> XEIGTPW_12607_full
>
>Summary
>
> FAILURE
>
> Serious unknown changes coming with XEIGTPW_12607_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in XEIGTPW_12607_full, please notify your bug team
> (I915-ci-infra@lists.freedesktop.org) to allow them
> to document this new failure mode, which will reduce false positives in
> CI.
>
>Participating hosts (4 -> 4)
>
> No changes in participating hosts
>
>Possible new issues
>
> Here are the unknown changes that may have been introduced in
> XEIGTPW_12607_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@kms_flip@2x-single-buffer-flip-vs-dpms-off-vs-modeset:
>
> * shard-bmg: NOTRUN -> [3]DMESG-WARN
>
> * {igt@xe_oa@buffer-size} (NEW):
>
> * shard-dg2-set2: NOTRUN -> [4]SKIP
Should we enable OA tests for dg2 as well? Your call. If not, then this
is just an expected skip.
Thanks,
Umesh
>
> Warnings
>
> * igt@xe_pm@s4-vm-bind-prefetch:
>
> * shard-lnl: [5]ABORT ([6]Intel XE#4268) -> [7]ABORT
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * {igt@kms_pipe_stress@stress-xrgb8888-ytiled}:
>
> * shard-bmg: NOTRUN -> [8]SKIP
> * shard-dg2-set2: NOTRUN -> [9]SKIP
> * shard-lnl: NOTRUN -> [10]SKIP
>
>New tests
>
> New tests have been introduced between XEIGT_8230_full and
> XEIGTPW_12607_full:
>
> New IGT tests (4)
>
> * igt@xe_oa@buffer-size:
>
> * Statuses : 2 pass(s) 1 skip(s)
> * Exec time: [0.0, 2.86] s
>
> * igt@xe_oa@buffer-size@ccs-0-16m:
>
> * Statuses : 1 pass(s)
> * Exec time: [2.80] s
>
> * igt@xe_oa@buffer-size@rcs-0-2m:
>
> * Statuses : 1 pass(s)
> * Exec time: [2.86] s
>
> * igt@xe_oa@unprivileged-single-ctx-counters@rcs-0:
>
> * Statuses : 2 pass(s)
> * Exec time: [0.07, 0.08] s
>
>Known issues
next prev parent reply other threads:[~2025-02-18 18:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 1:06 [PATCH 00/13] Some refactor, rewrite and fixes for OA tests Umesh Nerlige Ramappa
2025-02-15 1:06 ` [PATCH 01/13] tests/intel/xe_oa: Use static for global variables Umesh Nerlige Ramappa
2025-02-18 17:28 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 02/13] tests/intel/xe_oa: Drop unused macro Umesh Nerlige Ramappa
2025-02-18 17:32 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 03/13] tests/intel/xe_oa: Rename oa_exp_1_millisec to oa_exponent_default Umesh Nerlige Ramappa
2025-02-22 2:42 ` Dixit, Ashutosh
2025-02-22 3:35 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 04/13] tests/intel/xe_oa: Use default exponent for some tests Umesh Nerlige Ramappa
2025-02-22 2:43 ` Dixit, Ashutosh
2025-02-22 3:37 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 05/13] tests/intel/xe_oa: Use same render copy width and height across tests Umesh Nerlige Ramappa
2025-02-22 2:48 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 06/13] tests/intel/xe_oa: Rewrite the polling small buf test Umesh Nerlige Ramappa
2025-02-24 21:35 ` Dixit, Ashutosh
2025-02-25 4:26 ` Dixit, Ashutosh
2025-02-25 22:51 ` Umesh Nerlige Ramappa
2025-02-27 3:45 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 07/13] tests/intel/xe_oa: Simplify the buffer-fill test Umesh Nerlige Ramappa
2025-02-24 21:33 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 08/13] tests/intel/xe_oa: Use default buffer size for non-zero reason Umesh Nerlige Ramappa
2025-02-22 3:10 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 09/13] tests/intel/xe_oa: Test oa buffer sizes Umesh Nerlige Ramappa
2025-02-18 18:34 ` Dixit, Ashutosh
2025-02-18 18:38 ` Dixit, Ashutosh
2025-02-18 18:44 ` Umesh Nerlige Ramappa
2025-02-22 0:13 ` Dixit, Ashutosh
2025-02-22 1:12 ` Umesh Nerlige Ramappa
2025-02-22 3:14 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 10/13] tests/intel/xe_oa: Rewrite enable-disable test Umesh Nerlige Ramappa
2025-02-25 0:30 ` Dixit, Ashutosh
2025-02-25 2:54 ` Dixit, Ashutosh
2025-02-25 22:25 ` Umesh Nerlige Ramappa
2025-02-15 1:06 ` [PATCH 11/13] tests/intel/xe_oa: Enable unprivileged-single-ctx-counters and fix it Umesh Nerlige Ramappa
2025-02-25 3:53 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 12/13] tests/intel/xe_oa: Fix mmio_trigger_reports testing Umesh Nerlige Ramappa
2025-02-22 3:32 ` Dixit, Ashutosh
2025-02-15 1:06 ` [PATCH 13/13] tests/intel/xe_oa: Set boundaries for OA exponent test Umesh Nerlige Ramappa
2025-02-22 3:17 ` Dixit, Ashutosh
2025-02-15 2:09 ` ✓ Xe.CI.BAT: success for Some refactor, rewrite and fixes for OA tests Patchwork
2025-02-15 2:23 ` ✗ i915.CI.BAT: failure " Patchwork
2025-02-18 18:32 ` Umesh Nerlige Ramappa
2025-02-16 8:05 ` ✗ Xe.CI.Full: " Patchwork
2025-02-18 18:38 ` Umesh Nerlige Ramappa [this message]
2025-02-18 18:40 ` Dixit, Ashutosh
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=Z7TTk8Raw5CxwwwD@orsosgc001 \
--to=umesh.nerlige.ramappa@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