Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <igt-dev@lists.freedesktop.org>, <ashutosh.dixit@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for PMU: multi-tile support (rev4)
Date: Thu, 18 May 2023 23:44:03 -0700	[thread overview]
Message-ID: <ZGcas8WVVmM+78bE@orsosgc001.jf.intel.com> (raw)
In-Reply-To: <168445518199.26991.6517756659835619140@emeril.freedesktop.org>

Hi Ashutosh,

One of the SKIPs below is not expected,

On Fri, May 19, 2023 at 12:13:01AM +0000, Patchwork wrote:
>   Patch Details
>
>   Series:  PMU: multi-tile support (rev4)
>   URL:     [1]https://patchwork.freedesktop.org/series/117406/
>   State:   failure
>   Details: [2]https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8990/index.html
>
>         CI Bug Log - changes from CI_DRM_13160_full -> IGTPW_8990_full
>
>Summary
>
>   FAILURE
>
>   Serious unknown changes coming with IGTPW_8990_full absolutely need to be
>   verified manually.
>
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_8990_full, please notify your bug team to allow them
>   to document this new failure mode, which will reduce false positives in
>   CI.
>
>   External URL:
>   https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8990/index.html
>
>Participating hosts (7 -> 7)
>
>   No changes in participating hosts
>
>Possible new issues
>
>   Here are the unknown changes that may have been introduced in
>   IGTPW_8990_full:
>
>  IGT changes
>
>    Possible regressions
>
>     * igt@gem_ctx_isolation@preservation-s3@vcs0:
>
>          * shard-apl: [3]PASS -> [4]ABORT
>
>     * {igt@perf_pmu@frequency@gt0} (NEW):
>
>          * {shard-rkl}: NOTRUN -> [5]SKIP +1 similar issue

With this IGT series - https://patchwork.freedesktop.org/series/117406/, 
we do not have igt@perf_pmu@frequency test anymore. It is replaced by 
igt@perf_pmu@frequency@gt0 for all single tile platforms. For non-MTL 
platforms, gem_engine_to_gt_map() should just return 0.

>
>     * {igt@perf_pmu@rc6-all-gts} (NEW):
>
>          * {shard-dg1}: NOTRUN -> [6]SKIP +1 similar issue
>
>          * {shard-tglu}: NOTRUN -> [7]SKIP +2 similar issues

These are expected to skip.

Umesh
>
>New tests

  reply	other threads:[~2023-05-19  6:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 21:25 [igt-dev] [PATCH i-g-t v2 00/15] PMU: multi-tile support Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 01/15] perf_pmu: Support multi-tile in rc6 subtest Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 02/15] perf_pmu: Two new rc6 subtests Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 03/15] perf_pmu: Support multi-tile in frequency subtest Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 04/15] perf_pmu: Quiesce GPU if measuring idle busyness without spinner Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 05/15] perf_pmu: Use correct pmu config for multi-tile Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 06/15] intel_gpu_top: Add an array of freq and rc6 counters Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 07/15] intel_gpu_top: Determine number of tiles Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 08/15] intel_gpu_top: Capture freq and rc6 counters from each gt Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 09/15] intel_gpu_top: Switch pmu_counter to use aggregated values Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 10/15] intel_gpu_top: Add definitions for gt-specific items and groups Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 11/15] intel_gpu_top: Bump up size of groups to accomodate multi-gt Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 12/15] intel_gpu_top: Increase visibility for class_view Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 13/15] intel_gpu_top: Show gt specific values if requested Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 14/15] intel_gpu_top: Reduce one level of indent Umesh Nerlige Ramappa
2023-05-17 21:25 ` [igt-dev] [PATCH i-g-t v2 15/15] intel_gpu_top: Add gt specific values to header in interactive mode Umesh Nerlige Ramappa
2023-05-17 22:15 ` [igt-dev] ✗ Fi.CI.BAT: failure for PMU: multi-tile support (rev4) Patchwork
2023-05-18 12:04   ` Kamil Konieczny
2023-05-18 12:20     ` Yedireswarapu, SaiX Nandan
2023-05-18 12:19 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-05-19  0:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-05-19  6:44   ` Umesh Nerlige Ramappa [this message]
2023-05-19  8:39     ` Dixit, Ashutosh
2023-05-19 15:55       ` Umesh Nerlige Ramappa

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=ZGcas8WVVmM+78bE@orsosgc001.jf.intel.com \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=ashutosh.dixit@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