public inbox for intel-gfx@lists.freedesktop.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 drm/i915, drm/ttm: Update the ttm_move_memcpy() interface (rev3)
Date: Mon, 23 Aug 2021 15:38:02 +0000	[thread overview]
Message-ID: <2d5eca25472148279ecbaadc58361e42@intel.com> (raw)
In-Reply-To: <6e25f450ff25363bbc6a722c6342dfe85a9bf384.camel@linux.intel.com>

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

Re-reported.

Lakshmi.

From: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Sent: Monday, August 23, 2021 12:07 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915, drm/ttm: Update the ttm_move_memcpy() interface (rev3)

On Fri, 2021-08-13 at 20:28 +0000, Patchwork wrote:
Patch Details
Series:

drm/i915, drm/ttm: Update the ttm_move_memcpy() interface (rev3)

URL:

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

State:

failure

Details:

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

CI Bug Log - changes from CI_DRM_10482_full -> Patchwork_20819_full
Summary

FAILURE

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

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

Possible new issues

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

IGT changes
Possible regressions

  *   igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:

     *   shard-glk: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10482/shard-glk8/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20819/shard-glk5/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html>

Lakshmi, this failure is unrelated.

Thanks,
Thomas



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

  reply	other threads:[~2021-08-23 15:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13 14:43 [Intel-gfx] [PATCH v2 0/2] drm/i915, drm/ttm: Update the ttm_move_memcpy() interface Thomas Hellström
2021-08-13 14:43 ` [Intel-gfx] [PATCH v2 1/2] drm/i915/ttm: Reorganize the ttm move code somewhat Thomas Hellström
2021-08-13 14:43 ` [Intel-gfx] [PATCH v2 2/2] drm/ttm, drm/i915: Update ttm_move_memcpy for async use Thomas Hellström
2021-08-23  9:09   ` Christian König
2021-08-13 16:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915, drm/ttm: Update the ttm_move_memcpy() interface (rev3) Patchwork
2021-08-13 20:28 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-08-23  7:07   ` Thomas Hellström
2021-08-23 15:38     ` Vudum, Lakshminarayana [this message]
2021-08-23 15:23 ` [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=2d5eca25472148279ecbaadc58361e42@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox