From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
Lakshminarayana Vudum <lakshminarayana.vudum@intel.com>
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 09:07:10 +0200 [thread overview]
Message-ID: <6e25f450ff25363bbc6a722c6342dfe85a9bf384.camel@linux.intel.com> (raw)
In-Reply-To: <162888651810.17682.14943295616955640879@emeril.freedesktop.org>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
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_fullSummaryFAILURE
> 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 issuesHere are the unknown changes that may have been introduced in
> Patchwork_20819_full:
> IGT changesPossible regressions * igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
> - shard-glk: PASS -> FAIL
Lakshmi, this failure is unrelated.
Thanks,
Thomas
[-- Attachment #2: Type: text/html, Size: 2268 bytes --]
next prev parent reply other threads:[~2021-08-23 7:07 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 [this message]
2021-08-23 15:38 ` Vudum, Lakshminarayana
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=6e25f450ff25363bbc6a722c6342dfe85a9bf384.camel@linux.intel.com \
--to=thomas.hellstrom@linux.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