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 Avoid reading OA reports before they land (rev2)
Date: Wed, 7 Jun 2023 12:44:57 -0700	[thread overview]
Message-ID: <ZIDeOfzZKVVIBQx2@orsosgc001.jf.intel.com> (raw)
In-Reply-To: <168615962814.21184.14101376781239913842@emeril.freedesktop.org>

On Wed, Jun 07, 2023 at 05:40:28PM +0000, Patchwork wrote:
>   Patch Details
>
>Series:  Avoid reading OA reports before they land (rev2)
>URL:     [1]https://patchwork.freedesktop.org/series/118886/
>State:   failure
>Details: [2]https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118886v2/index.html
>
>     CI Bug Log - changes from CI_DRM_13238_full -> Patchwork_118886v2_full
>
>Summary
>
>   FAILURE
>
>   Serious unknown changes coming with Patchwork_118886v2_full absolutely
>   need to be
>   verified manually.
>
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_118886v2_full, please notify your bug team to
>   allow them
>   to document this new failure mode, which will reduce false positives in
>   CI.
>
>Participating hosts (7 -> 7)
>
>   No changes in participating hosts
>
>Possible new issues
>
>   Here are the unknown changes that may have been introduced in
>   Patchwork_118886v2_full:
>
>  IGT changes
>
>    Possible regressions
>
>     * igt@kms_vblank@pipe-b-accuracy-idle:
>
>          * shard-glk: [3]PASS -> [4]FAIL

Unrelated to this patch since no OA use cases in the above test path.  

Umesh

>
>Known issues
>

      reply	other threads:[~2023-06-07 19:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 19:39 [Intel-gfx] [PATCH v4 0/2] Avoid reading OA reports before they land Umesh Nerlige Ramappa
2023-06-05 19:39 ` [Intel-gfx] [PATCH v4 1/2] i915/perf: Drop the aging_tail logic in perf OA Umesh Nerlige Ramappa
2023-06-05 19:39 ` [Intel-gfx] [PATCH v4 2/2] i915/perf: Do not add ggtt offset to hw_tail Umesh Nerlige Ramappa
2023-06-05 23:25 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Avoid reading OA reports before they land Patchwork
2023-06-05 23:44 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-06-07 19:25   ` Umesh Nerlige Ramappa
2023-06-07  1:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Avoid reading OA reports before they land (rev2) Patchwork
2023-06-07  1:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-07 17:40 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-06-07 19:44   ` Umesh Nerlige Ramappa [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=ZIDeOfzZKVVIBQx2@orsosgc001.jf.intel.com \
    --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