Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.IGT: failure for i915/pmu: Move execlist stats initialization to execlist specific setup (rev2)
Date: Fri, 15 Sep 2023 09:02:05 -0700	[thread overview]
Message-ID: <ZQR//dkXOLpVcdZC@unerlige-ril> (raw)
In-Reply-To: <169466511430.29164.10915444125829854058@emeril.freedesktop.org>

On Thu, Sep 14, 2023 at 04:18:34AM +0000, Patchwork wrote:
>   Patch Details
>
>Series:  i915/pmu: Move execlist stats initialization to execlist specific setup
>         (rev2)
>URL:     [1]https://patchwork.freedesktop.org/series/123616/
>State:   failure
>Details: [2]https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123616v2/index.html
>
>     CI Bug Log - changes from CI_DRM_13627_full -> Patchwork_123616v2_full
>
>Summary
>
>   FAILURE
>
>   Serious unknown changes coming with Patchwork_123616v2_full absolutely
>   need to be
>   verified manually.
>
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_123616v2_full, please notify your bug team
>   (lgci.bug.filing@intel.com) to allow them
>   to document this new failure mode, which will reduce false positives in
>   CI.
>
>Participating hosts (9 -> 10)
>
>   Additional (1): shard-tglu0
>
>Possible new issues
>
>   Here are the unknown changes that may have been introduced in
>   Patchwork_123616v2_full:
>
>  IGT changes
>
>    Possible regressions
>
>     * igt@perf_pmu@rc6-all-gts:
>
>          * shard-mtlp: NOTRUN -> [3]ABORT

This is an existing bug and not related to this patch:

https://patchwork.freedesktop.org/series/123616/#rev2

Thanks,
Umesh
>
>    Suppressed
>
>   The following results come from untrusted machines, tests, or statuses.
>   They do not affect the overall result.
>
>     * {igt@kms_feature_discovery@display-4x}:
>
>          * shard-mtlp: NOTRUN -> [4]SKIP
>
>New tests
>
>   New tests have been introduced between CI_DRM_13627_full and
>   Patchwork_123616v2_full:
>
>  New IGT tests (4)
>
>     * igt@kms_atomic_transition@plane-all-transition-nonblocking@pipe-a-hdmi-a-4:
>
>          * Statuses : 1 pass(s)
>          * Exec time: [0.0] s
>
>     * igt@kms_atomic_transition@plane-all-transition-nonblocking@pipe-b-hdmi-a-4:
>
>          * Statuses : 1 pass(s)
>          * Exec time: [0.0] s
>
>     * igt@kms_cursor_crc@cursor-onscreen-128x128@pipe-a-hdmi-a-4:
>
>          * Statuses : 1 pass(s)
>          * Exec time: [0.0] s
>
>     * igt@kms_cursor_crc@cursor-onscreen-128x128@pipe-d-hdmi-a-4:
>
>          * Statuses : 1 pass(s)
>          * Exec time: [0.0] s
>
>Known issues
>
...

  reply	other threads:[~2023-09-15 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 21:22 [Intel-gfx] [PATCH] i915/pmu: Move execlist stats initialization to execlist specific setup Umesh Nerlige Ramappa
2023-09-12 22:54 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2023-09-13 20:50 ` [Intel-gfx] [PATCH] " Teres Alexis, Alan Previn
2023-09-13 23:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for i915/pmu: Move execlist stats initialization to execlist specific setup (rev2) Patchwork
2023-09-14  4:18 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-15 16:02   ` Umesh Nerlige Ramappa [this message]
2023-09-15 16:39     ` 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=ZQR//dkXOLpVcdZC@unerlige-ril \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=intel-gfx@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