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: warning for igt/tools_test: Check the tools exist before executing
Date: Tue, 12 Dec 2017 18:45:52 -0000	[thread overview]
Message-ID: <20171212184552.16343.29253@emeril.freedesktop.org> (raw)
In-Reply-To: <20171212172201.30788-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: igt/tools_test: Check the tools exist before executing
URL   : https://patchwork.freedesktop.org/series/35237/
State : warning

== Summary ==

Test kms_frontbuffer_tracking:
        Subgroup fbc-1p-offscren-pri-shrfb-draw-render:
                pass       -> FAIL       (shard-snb) fdo#101623
Test drm_read:
        Subgroup short-buffer-block:
                pass       -> SKIP       (shard-hsw)
Test kms_properties:
        Subgroup crtc-properties-atomic:
                pass       -> SKIP       (shard-hsw) fdo#103706
Test kms_busy:
        Subgroup extended-modeset-hang-oldfb-render-c:
                pass       -> SKIP       (shard-hsw)
Test tools_test:
        Subgroup tools_test:
                pass       -> SKIP       (shard-snb)
                pass       -> SKIP       (shard-hsw)
Test gem_tiled_swapping:
        Subgroup non-threaded:
                incomplete -> PASS       (shard-snb) fdo#104009

fdo#101623 https://bugs.freedesktop.org/show_bug.cgi?id=101623
fdo#103706 https://bugs.freedesktop.org/show_bug.cgi?id=103706
fdo#104009 https://bugs.freedesktop.org/show_bug.cgi?id=104009

shard-hsw        total:2712 pass:1533 dwarn:1   dfail:0   fail:10  skip:1168 time:9488s
shard-snb        total:2712 pass:1308 dwarn:1   dfail:0   fail:12  skip:1391 time:8111s
Blacklisted hosts:
shard-apl        total:2618 pass:1617 dwarn:1   dfail:0   fail:23  skip:976 time:12974s

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_658/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-12 18:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 17:22 [PATCH igt] igt/tools_test: Check the tools exist before executing Chris Wilson
2017-12-12 17:39 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-12-12 18:45 ` Patchwork [this message]
2017-12-13  9:53 ` [PATCH igt] " Petri Latvala
2017-12-13 10:48 ` Joonas Lahtinen
2017-12-13 14:56 ` [PATCH igt v2] " Chris Wilson
2017-12-14 11:11   ` Petri Latvala
2017-12-14 11:14     ` Chris Wilson
2017-12-14 11:20       ` Petri Latvala
2017-12-14 11:24         ` Chris Wilson
2017-12-14 12:39           ` Petri Latvala
2017-12-13 17:16 ` ✓ Fi.CI.BAT: success for igt/tools_test: Check the tools exist before executing (rev2) Patchwork
2017-12-13 18:59 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-12-14 11:39 ` [PATCH igt v3] igt/tools_test: Check the tools exist before executing Chris Wilson
2017-12-14 11:57 ` ✗ Fi.CI.BAT: warning for igt/tools_test: Check the tools exist before executing (rev3) Patchwork
2017-12-14 21:57 ` ✓ Fi.CI.BAT: success " Patchwork
2017-12-14 23:38 ` ✗ Fi.CI.IGT: failure " 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=20171212184552.16343.29253@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