Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: warning for series starting with [1/3] lib/dummyload: Support returning output fence
Date: Tue, 19 Dec 2017 21:29:07 -0000	[thread overview]
Message-ID: <20171219212907.32030.82254@emeril.freedesktop.org> (raw)
In-Reply-To: <20171219154543.10648-1-tvrtko.ursulin@linux.intel.com>

== Series Details ==

Series: series starting with [1/3] lib/dummyload: Support returning output fence
URL   : https://patchwork.freedesktop.org/series/35589/
State : warning

== Summary ==

Test pm_rpm:
        Subgroup system-suspend-modeset:
                pass       -> SKIP       (shard-hsw)
Test kms_draw_crc:
        Subgroup draw-method-xrgb2101010-mmap-gtt-untiled:
                skip       -> PASS       (shard-snb)
Test perf:
        Subgroup blocking:
                fail       -> PASS       (shard-hsw) fdo#102252
Test kms_atomic_transition:
        Subgroup 1x-modeset-transitions-nonblocking:
                skip       -> PASS       (shard-snb)
Test kms_busy:
        Subgroup extended-pageflip-hang-oldfb-render-b:
                skip       -> PASS       (shard-snb)
Test kms_rotation_crc:
        Subgroup sprite-rotation-180:
                pass       -> SKIP       (shard-snb)
Test kms_flip:
        Subgroup vblank-vs-modeset-suspend:
                skip       -> PASS       (shard-snb) fdo#102365

fdo#102252 https://bugs.freedesktop.org/show_bug.cgi?id=102252
fdo#102365 https://bugs.freedesktop.org/show_bug.cgi?id=102365

shard-hsw        total:2727 pass:1536 dwarn:1   dfail:0   fail:10  skip:1180 time:9422s
shard-snb        total:2727 pass:1309 dwarn:1   dfail:0   fail:10  skip:1407 time:8096s
Blacklisted hosts:
shard-apl        total:2727 pass:1690 dwarn:1   dfail:0   fail:31  skip:1004 time:13803s
shard-kbl        total:2709 pass:1803 dwarn:4   dfail:0   fail:28  skip:873 time:10895s

== Logs ==

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

  parent reply	other threads:[~2017-12-19 21:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 15:45 [PATCH i-g-t 1/3] lib/dummyload: Support returning output fence Tvrtko Ursulin
2017-12-19 15:45 ` [PATCH i-g-t 2/3] tests/perf_pmu: Simplify interrupt testing Tvrtko Ursulin
2017-12-19 21:43   ` Chris Wilson
2017-12-19 21:45   ` Chris Wilson
2017-12-20  9:45     ` Tvrtko Ursulin
2017-12-20 10:49       ` Chris Wilson
2017-12-20 12:35         ` Tvrtko Ursulin
2017-12-20 12:39           ` Chris Wilson
2017-12-19 15:45 ` [PATCH i-g-t 3/3] tests/perf_pmu: Verify engine busyness accuracy Tvrtko Ursulin
2017-12-19 22:45   ` Chris Wilson
2017-12-20  9:48     ` Tvrtko Ursulin
2017-12-19 17:46 ` ✓ Fi.CI.BAT: success for series starting with [1/3] lib/dummyload: Support returning output fence Patchwork
2017-12-19 21:29 ` Patchwork [this message]
2017-12-19 22:42 ` [PATCH i-g-t 1/3] " Chris Wilson
2017-12-20  9:44   ` Tvrtko Ursulin

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=20171219212907.32030.82254@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tursulin@ursulin.net \
    /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