All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Skip object locking around a no-op set-domain ioctl
Date: Thu, 21 Mar 2019 09:11:30 +0000	[thread overview]
Message-ID: <155315949025.22764.6833417356236694769@skylake-alporthouse-com> (raw)
In-Reply-To: <20190321090459.14934.30165@emeril.freedesktop.org>

Quoting Patchwork (2019-03-21 09:04:59)
> == Series Details ==
> 
> Series: drm/i915: Skip object locking around a no-op set-domain ioctl
> URL   : https://patchwork.freedesktop.org/series/58325/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_5785 -> Patchwork_12542
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_12542 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_12542, please notify your bug team to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   External URL: https://patchwork.freedesktop.org/api/1.0/series/58325/revisions/1/mbox/
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in Patchwork_12542:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_exec_reloc@basic-cpu-active:
>     - fi-bsw-kefka:       PASS -> FAIL +7
>     - fi-hsw-4770r:       PASS -> FAIL +3
>     - fi-cfl-8109u:       PASS -> FAIL +3
>     - fi-byt-clapper:     PASS -> FAIL +7
>     - fi-ivb-3770:        PASS -> FAIL +3
>     - fi-icl-u3:          PASS -> FAIL +3
>     - fi-skl-gvtdvm:      PASS -> FAIL +2

Intriguing, now that might explain some of the random failure we've
seen here over the years, as we unexpectedly take the slow path.

>   * igt@prime_vgem@basic-fence-mmap:
>     - fi-cfl-8700k:       PASS -> FAIL +3
>     - fi-skl-iommu:       PASS -> FAIL +3
>     - fi-cfl-guc:         PASS -> FAIL +3
>     - fi-skl-6770hq:      PASS -> FAIL +3
>     - fi-skl-6260u:       PASS -> FAIL +3
>     - fi-kbl-r:           PASS -> FAIL +3

Hmm. Decidedly, hmm.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-03-21  9:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  8:05 [PATCH] drm/i915: Skip object locking around a no-op set-domain ioctl Chris Wilson
2019-03-21  8:41 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-03-21  9:04 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-03-21  9:11   ` Chris Wilson [this message]
2019-03-21  9:21     ` Chris Wilson
2019-03-21  9:14 ` [PATCH] " Chris Wilson
2019-03-21  9:17 ` Chris Wilson
2019-03-21  9:35 ` [PATCH v3] " Chris Wilson
2019-03-21  9:44 ` [PATCH v4] " Chris Wilson
2019-03-21 12:36 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Skip object locking around a no-op set-domain ioctl (rev4) Patchwork
2019-03-21 12:59 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-22  1:31 ` ✓ 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=155315949025.22764.6833417356236694769@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=patchwork@emeril.freedesktop.org \
    /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.