All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.IGT: failure for series starting with [v3,1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks
Date: Mon, 8 Nov 2021 18:25:09 +0000	[thread overview]
Message-ID: <cc16fa7b506d44f78865d3b5cce096fc@intel.com> (raw)
In-Reply-To: <efb2ff5f-acf7-df24-e516-c2fe0df701bd@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]

Below issue filed and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/4457
igt@kms_flip@basic-flip-vs-dpms@c-edp1 - incomplete - No warnings/errors

Lakshmi.
From: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Sent: Monday, November 8, 2021 12:10 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [v3,1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks



On 11/5/21 17:55, Patchwork wrote:
Patch Details
Series:

series starting with [v3,1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks

URL:

https://patchwork.freedesktop.org/series/96615/

State:

failure

Details:

https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21526/index.html

CI Bug Log - changes from CI_DRM_10846_full -> Patchwork_21526_full
Summary

FAILURE

Serious unknown changes coming with Patchwork_21526_full absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_21526_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.

Participating hosts (11 -> 11)

No changes in participating hosts

Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21526_full:

IGT changes
Possible regressions

  *   igt@kms_flip@basic-flip-vs-dpms@c-edp1:

     *   shard-tglb: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10846/shard-tglb3/igt@kms_flip@basic-flip-vs-dpms@c-edp1.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21526/shard-tglb6/igt@kms_flip@basic-flip-vs-dpms@c-edp1.html>

Lakshmi,

This failure is unrelated.

Thanks,

Thomas



[-- Attachment #2: Type: text/html, Size: 13770 bytes --]

  reply	other threads:[~2021-11-08 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 15:01 [Intel-gfx] [PATCH v3 1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks Thomas Hellström
2021-11-05 15:01 ` [Intel-gfx] [PATCH v3 2/2] HAX: drm/i915/selftest: Temporarily avoid tainting the kernel on engine reset failure Thomas Hellström
2021-11-05 15:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v3,1/2] drm/i915/selftests: Use clear_and_wake_up_bit() for the per-engine reset bitlocks Patchwork
2021-11-05 16:55 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-08  8:09   ` Thomas Hellström
2021-11-08 18:25     ` Vudum, Lakshminarayana [this message]
2021-11-08 16:43 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork

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=cc16fa7b506d44f78865d3b5cce096fc@intel.com \
    --to=lakshminarayana.vudum@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=thomas.hellstrom@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.