public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>, ",
	Lakshminarayana Vudum" <lakshminarayana.vudum@intel.com>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.IGT: failure for drm/i915/ttm: Async migration (rev11)
Date: Wed, 24 Nov 2021 11:56:09 +0100	[thread overview]
Message-ID: <a93c6a57-0c13-b6f6-6188-58e83f85d491@linux.intel.com> (raw)
In-Reply-To: <163774693406.25295.4750352332692397734@emeril.freedesktop.org>

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


On 11/24/21 10:42, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* 	drm/i915/ttm: Async migration (rev11)
> *URL:* 	https://patchwork.freedesktop.org/series/96798/
> *State:* 	failure
> *Details:* 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21672/index.html
>
>
>   CI Bug Log - changes from CI_DRM_10921_full -> Patchwork_21672_full
>
>
>     Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_21672_full absolutely 
> need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_21672_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_21672_full:
>
>
>       IGT changes
>
>
>         Possible regressions
>
>  *
>
>     igt@gem_exec_capture@pi@rcs0:
>
>       o shard-skl: PASS
>         <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10921/shard-skl7/igt@gem_exec_capture@pi@rcs0.html>
>         -> INCOMPLETE
>         <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21672/shard-skl2/igt@gem_exec_capture@pi@rcs0.html>
>  *
>
>     igt@gem_exec_create@forked@smem:
>
>       o shard-kbl: NOTRUN -> INCOMPLETE
>         <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21672/shard-kbl7/igt@gem_exec_create@forked@smem.html>
>  *
>
>     igt@kms_atomic_interruptible@universal-setplane-cursor@dp-1-pipe-a:
>
>       o shard-kbl: PASS
>         <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10921/shard-kbl1/igt@kms_atomic_interruptible@universal-setplane-cursor@dp-1-pipe-a.html>
>         -> INCOMPLETE
>         <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21672/shard-kbl7/igt@kms_atomic_interruptible@universal-setplane-cursor@dp-1-pipe-a.html>
>         +2 similar issues
>
Lakshmi,

These failures are unrelated. The first one appears also elsewhere, The 
other two appears to be a general problem with shard-kbl. Lots of random 
hangs from that one.

/Thomas


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

  reply	other threads:[~2021-11-24 10:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 21:45 [Intel-gfx] [PATCH v7 0/6] drm/i915/ttm: Async migration Thomas Hellström
2021-11-22 21:45 ` [Intel-gfx] [PATCH v7 1/6] drm/i915: Add support for moving fence waiting Thomas Hellström
2021-11-22 21:45 ` [Intel-gfx] [PATCH v7 2/6] drm/i915/ttm: Move the i915_gem_obj_copy_ttm() function Thomas Hellström
2021-11-22 21:45 ` [Intel-gfx] [PATCH v7 3/6] drm/i915/ttm: Drop region reference counting Thomas Hellström
2021-11-22 21:45 ` [Intel-gfx] [PATCH v7 4/6] drm/i915/ttm: Correctly handle waiting for gpu when shrinking Thomas Hellström
2021-11-22 21:45 ` [Intel-gfx] [PATCH v7 5/6] drm/i915/ttm: Implement asynchronous TTM moves Thomas Hellström
2021-11-22 21:45 ` [Intel-gfx] [PATCH v7 6/6] drm/i915/ttm: Update i915_gem_obj_copy_ttm() to be asynchronous Thomas Hellström
2021-11-22 22:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ttm: Async migration (rev8) Patchwork
2021-11-22 22:49 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-11-23  6:27 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ttm: Async migration (rev9) Patchwork
2021-11-23  6:58 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-11-23  7:37 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ttm: Async migration (rev10) Patchwork
2021-11-23  8:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-23  9:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-24  7:50 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ttm: Async migration (rev11) Patchwork
2021-11-24  8:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-24  9:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-24 10:56   ` Thomas Hellström [this message]
2021-11-24 15:51     ` Thomas Hellström
2021-11-24 20:16     ` Vudum, Lakshminarayana
2021-11-24 18:48 ` Patchwork
2021-11-24 18:55 ` Patchwork
2021-11-24 19:12 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2021-11-25  8:42 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ttm: Async migration (rev12) Patchwork
2021-11-25  9:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-25 10:27 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=a93c6a57-0c13-b6f6-6188-58e83f85d491@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