Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: failure for drm/i915/execlists: Move the GEM_BUG_ON context matches CSB later
Date: Wed, 21 Feb 2018 20:19:28 -0000	[thread overview]
Message-ID: <20180221201928.14809.78808@emeril.freedesktop.org> (raw)
In-Reply-To: <20180221152301.9178-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915/execlists: Move the GEM_BUG_ON context matches CSB later
URL   : https://patchwork.freedesktop.org/series/38709/
State : failure

== Summary ==

Test kms_plane_multiple:
        Subgroup legacy-pipe-b-tiling-none:
                skip       -> PASS       (shard-snb)
Test kms_vblank:
        Subgroup pipe-b-wait-busy-hang:
                skip       -> PASS       (shard-snb)
Test kms_flip:
        Subgroup 2x-flip-vs-absolute-wf_vblank-interruptible:
                fail       -> PASS       (shard-hsw) fdo#100368 +1
        Subgroup 2x-dpms-vs-vblank-race:
                pass       -> FAIL       (shard-hsw) fdo#103060
Test kms_pipe_crc_basic:
        Subgroup read-crc-pipe-c-frame-sequence:
                fail       -> PASS       (shard-apl) fdo#103481
Test gem_eio:
        Subgroup suspend:
                pass       -> INCOMPLETE (shard-hsw) fdo#105055
        Subgroup in-flight:
                incomplete -> PASS       (shard-apl)
        Subgroup in-flight-external:
                pass       -> INCOMPLETE (shard-apl)
Test kms_cursor_crc:
        Subgroup cursor-128x128-suspend:
                pass       -> INCOMPLETE (shard-hsw) fdo#103540
Test kms_atomic_transition:
        Subgroup 1x-modeset-transitions-nonblocking-fencing:
                fail       -> PASS       (shard-apl) fdo#103207

fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
fdo#103060 https://bugs.freedesktop.org/show_bug.cgi?id=103060
fdo#103481 https://bugs.freedesktop.org/show_bug.cgi?id=103481
fdo#105055 https://bugs.freedesktop.org/show_bug.cgi?id=105055
fdo#103540 https://bugs.freedesktop.org/show_bug.cgi?id=103540
fdo#103207 https://bugs.freedesktop.org/show_bug.cgi?id=103207

shard-apl        total:3275 pass:1712 dwarn:1   dfail:0   fail:13  skip:1547 time:11710s
shard-hsw        total:3422 pass:1743 dwarn:1   dfail:0   fail:3   skip:1672 time:11273s
shard-snb        total:3464 pass:1356 dwarn:1   dfail:0   fail:3   skip:2104 time:6627s
Blacklisted hosts:
shard-kbl        total:3464 pass:1960 dwarn:1   dfail:0   fail:15  skip:1488 time:9697s

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8107/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-02-21 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 15:23 [PATCH] drm/i915/execlists: Move the GEM_BUG_ON context matches CSB later Chris Wilson
2018-02-21 16:06 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-21 20:19 ` Patchwork [this message]
2018-02-22  8:51 ` [PATCH] " Mika Kuoppala
2018-02-22  9:09   ` Chris Wilson

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=20180221201928.14809.78808@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox