intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Date: Wed, 27 Jan 2021 07:37:43 +0000	[thread overview]
Message-ID: <1b91e8b2003f4f2bbdac6a9f06ede430@intel.com> (raw)
In-Reply-To: <15ac9308013f44b59f7fce1c9bbcd505@intel.com>



> -----Original Message-----
> From: Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
> Sent: Wednesday, January 27, 2021 11:00 AM
> To: Gupta, Anshuman <anshuman.gupta@intel.com>; intel-
> gfx@lists.freedesktop.org
> Cc: Sean Paul <sean@poorly.run>
> Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the
> QSES check for HDCP 1.4 over MST (rev2)
> 
> Re-reporting will just re-report the results once more time. Re-reporting will
> re-check if there is an existing bug for the regression failures or not. If a bug
> is found, series shows as success (as the failure is not a regression).
> Regression failures will find a bug when a re-report as I either file a new bug
> or I will associate the regression failure to an existing bug before I re-report.
> 
> But re-reporting will not trigger re-run to see version 2 results. Let me know
> if you have any further questions.
We don't have CI-IGT (full) results for the series https://patchwork.freedesktop.org/series/85555/#rev2 yet.
In order to merge this patch we would require CI pre merge results.
Thanks,
Anshuman Gupta.
> 
> Thanks,
> Lakshmi.
> -----Original Message-----
> From: Gupta, Anshuman <anshuman.gupta@intel.com>
> Sent: Tuesday, January 26, 2021 9:20 PM
> To: Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>; intel-
> gfx@lists.freedesktop.org
> Cc: Sean Paul <sean@poorly.run>
> Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the
> QSES check for HDCP 1.4 over MST (rev2)
> 
> Thanks Lakshmi for re-reporting it.
> May I know that re-reporting will also trigger a CI-IGT run.
> I am not able to see this series in CI Queue https://intel-gfx-
> ci.01.org/queue/index.html
> Currently this patch Rev2 is not showing any CI-IGT results.
> 
> Br,
> Anshuman
> 
> > -----Original Message-----
> > From: Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
> > Sent: Monday, January 25, 2021 10:40 PM
> > To: Gupta, Anshuman <anshuman.gupta@intel.com>; intel-
> > gfx@lists.freedesktop.org
> > Cc: Sean Paul <sean@poorly.run>
> > Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
> > Disable the QSES check for HDCP 1.4 over MST (rev2)
> >
> > Re-reported.
> >
> > -----Original Message-----
> > From: Gupta, Anshuman <anshuman.gupta@intel.com>
> > Sent: Monday, January 25, 2021 7:26 AM
> > To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
> > <lakshminarayana.vudum@intel.com>
> > Cc: Sean Paul <sean@poorly.run>
> > Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
> > Disable the QSES check for HDCP 1.4 over MST (rev2)
> >
> > Hi Lakshmi ,
> > We need to merge the patch
> > https://patchwork.freedesktop.org/series/85555/
> > Below are the gem failures causing the BAT to fail , those were not
> > seen on
> > Rev1 of this patch.
> > Could you please rereport-the results to trigger CI-IGT run.
> > Thanks,
> > Anshuman Gupta.
> >
> > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of
> > Patchwork
> > Sent: Friday, January 22, 2021 8:13 AM
> > To: Sean Paul <sean@poorly.run>
> > Cc: intel-gfx@lists.freedesktop.org
> > Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable
> > the QSES check for HDCP 1.4 over MST (rev2)
> >
> > Patch Details
> > Series:
> > drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
> > URL:
> > https://patchwork.freedesktop.org/series/85555/
> > State:
> > failure
> > Details:
> > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
> > CI Bug Log - changes from CI_DRM_9666 -> Patchwork_19447 Summary
> > FAILURE Serious unknown changes coming with Patchwork_19447
> absolutely
> > need to be verified manually.
> > If you think the reported changes have nothing to do with the changes
> > introduced in Patchwork_19447, 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/Patchwork_19447/index.html
> > Possible new issues
> > Here are the unknown changes that may have been introduced in
> > Patchwork_19447:
> > IGT changes
> > Possible regressions
> > • igt@i915_selftest@live@gt_lrc:
> > o fi-bsw-n3050:
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
> > bsw-n3050/igt@i915_selftest@live@gt_lrc.html -> https://intel-gfx-
> > ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-
> > n3050/igt@i915_selftest@live@gt_lrc.html
> > Known issues
> > Here are the changes found in Patchwork_19447 that come from known
> > issues:
> > IGT changes
> > Issues hit
> > • igt@gem_mmap_gtt@basic:
> > o fi-tgl-y:
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
> > y/igt@gem_mmap_gtt@basic.html -> https://intel-gfx-
> ci.01.org/tree/drm-
> > tip/Patchwork_19447/fi-tgl-y/igt@gem_mmap_gtt@basic.html
> > (https://gitlab.freedesktop.org/drm/intel/issues/402) +2 similar
> > issues •
> > igt@i915_selftest@live@hugepages:
> > o fi-bsw-n3050:
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
> > bsw-n3050/igt@i915_selftest@live@hugepages.html -> https://intel-gfx-
> > ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-
> > n3050/igt@i915_selftest@live@hugepages.html
> > (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +20 similar
> > issues • igt@i915_selftest@live@ring_submission:
> > o fi-bsw-n3050: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-
> > tip/Patchwork_19447/fi-bsw-
> > n3050/igt@i915_selftest@live@ring_submission.html
> > (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +2 similar
> > issues • igt@kms_chamelium@dp-crc-fast:
> > o fi-kbl-7500u:
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
> > kbl-7500u/igt@kms_chamelium@dp-crc-fast.html -> https://intel-gfx-
> > ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl-
> > 7500u/igt@kms_chamelium@dp-crc-fast.html
> > (https://gitlab.freedesktop.org/drm/intel/issues/1161 /
> > https://gitlab.freedesktop.org/drm/intel/issues/262)
> > Possible fixes
> > • igt@gem_tiled_blits@basic:
> > o fi-tgl-y:
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
> > y/igt@gem_tiled_blits@basic.html
> > (https://gitlab.freedesktop.org/drm/intel/issues/402) ->
> > https://intel-gfx-
> > ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-
> > y/igt@gem_tiled_blits@basic.html +1 similar issue Warnings •
> > igt@i915_selftest@live@execlists:
> > o fi-bsw-n3050:
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
> > bsw-n3050/igt@i915_selftest@live@execlists.html
> > (https://gitlab.freedesktop.org/drm/intel/issues/2940) ->
> > https://intel-gfx-
> > ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-
> > n3050/igt@i915_selftest@live@execlists.html
> > (https://bugs.freedesktop.org/show_bug.cgi?id=109271)
> > Participating hosts (41 -> 37)
> > Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u Build
> > changes • Linux: CI_DRM_9666 -> Patchwork_19447
> > CI-20190529: 20190529
> > CI_DRM_9666: 9ccbc653bf2948d1f7e9ff300dd7679b888ffa25 @
> > git://anongit.freedesktop.org/gfx-ci/linux
> > IGT_5962: 22e3daaed82ab7890018a2f2aabf5082cd536023 @
> > git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> > Patchwork_19447: 69d7db003fa406df7851ab08239dd409a78f4421 @
> > git://anongit.freedesktop.org/gfx-ci/linux
> > == Linux commits ==
> > 69d7db003fa4 drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over
> > MST
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-01-27  7:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 22:38 [Intel-gfx] [PATCH] drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST Sean Paul
2021-01-06 23:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-01-07 10:13 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-01-12 17:51 ` [Intel-gfx] [PATCH] " Jani Nikula
2021-01-13 10:19 ` Anshuman Gupta
2021-01-13 13:39   ` Sean Paul
2021-01-13 14:31     ` Daniel Vetter
2021-01-13 18:33       ` Sean Paul
2021-01-13 20:45         ` Daniel Vetter
2021-01-15 10:22         ` Gupta, Anshuman
2021-01-21 17:26 ` [Intel-gfx] [PATCH v2] " Sean Paul
2021-01-22  2:42 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2) Patchwork
2021-01-25 15:26   ` Gupta, Anshuman
2021-01-25 16:41     ` Vudum, Lakshminarayana
2021-01-25 17:10     ` Vudum, Lakshminarayana
2021-01-27  5:20       ` Gupta, Anshuman
2021-01-27  5:29         ` Vudum, Lakshminarayana
2021-01-27  7:37           ` Gupta, Anshuman [this message]
2021-01-27 19:13             ` Vudum, Lakshminarayana
2021-01-28  7:09               ` Petri Latvala
2021-01-25 17:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-28  7:05 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-01-28  7:22   ` Gupta, Anshuman

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=1b91e8b2003f4f2bbdac6a9f06ede430@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lakshminarayana.vudum@intel.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;
as well as URLs for NNTP newsgroup(s).