All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.IGT: warning for tests/perf_pmu: Avoid RT thread for accuracy test
Date: Mon, 26 Mar 2018 13:04:15 -0000	[thread overview]
Message-ID: <20180326130415.7436.37351@emeril.freedesktop.org> (raw)
In-Reply-To: <20180326105758.5211-1-tvrtko.ursulin@linux.intel.com>

== Series Details ==

Series: tests/perf_pmu: Avoid RT thread for accuracy test
URL   : https://patchwork.freedesktop.org/series/40662/
State : warning

== Summary ==

---- Possible new issues:

Test kms_flip:
        Subgroup 2x-single-buffer-flip-vs-dpms-off-vs-modeset:
                pass       -> DMESG-WARN (shard-hsw)

---- Known issues:

Test kms_flip:
        Subgroup 2x-flip-vs-expired-vblank-interruptible:
                fail       -> PASS       (shard-hsw) fdo#102887
        Subgroup 2x-plain-flip-fb-recreate-interruptible:
                pass       -> FAIL       (shard-hsw) fdo#100368 +1
        Subgroup dpms-vs-vblank-race-interruptible:
                fail       -> PASS       (shard-hsw) fdo#103060 +2
Test kms_plane_multiple:
        Subgroup atomic-pipe-a-tiling-x:
                fail       -> PASS       (shard-snb) fdo#103166
Test kms_rotation_crc:
        Subgroup sprite-rotation-180:
                fail       -> PASS       (shard-snb) fdo#103925
Test kms_setmode:
        Subgroup basic:
                pass       -> FAIL       (shard-apl) fdo#99912
Test kms_vblank:
        Subgroup pipe-a-accuracy-idle:
                pass       -> FAIL       (shard-hsw) fdo#102583

fdo#102887 https://bugs.freedesktop.org/show_bug.cgi?id=102887
fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
fdo#103060 https://bugs.freedesktop.org/show_bug.cgi?id=103060
fdo#103166 https://bugs.freedesktop.org/show_bug.cgi?id=103166
fdo#103925 https://bugs.freedesktop.org/show_bug.cgi?id=103925
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
fdo#102583 https://bugs.freedesktop.org/show_bug.cgi?id=102583

shard-apl        total:3495 pass:1831 dwarn:1   dfail:0   fail:7   skip:1655 time:12795s
shard-hsw        total:3495 pass:1780 dwarn:2   dfail:0   fail:3   skip:1709 time:11646s
shard-snb        total:3495 pass:1375 dwarn:1   dfail:0   fail:2   skip:2117 time:6961s
Blacklisted hosts:
shard-kbl        total:3477 pass:1937 dwarn:1   dfail:0   fail:9   skip:1529 time:9473s

== Logs ==

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

  parent reply	other threads:[~2018-03-26 13:04 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 10:57 [CI i-g-t] tests/perf_pmu: Avoid RT thread for accuracy test Tvrtko Ursulin
2018-03-26 10:57 ` [Intel-gfx] " Tvrtko Ursulin
2018-03-26 11:17 ` [igt-dev] " Chris Wilson
2018-03-26 11:17   ` Chris Wilson
2018-03-26 12:40   ` Tvrtko Ursulin
2018-03-26 12:40     ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-03-26 11:23 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-03-26 13:04 ` Patchwork [this message]
2018-03-27 14:31 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2018-03-27 17:08 ` [igt-dev] ✗ Fi.CI.BAT: warning " Patchwork
2018-03-28  9:22 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-03-28 14:36 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-03-28 16:56   ` Tvrtko Ursulin
2018-03-28 17:10     ` Chris Wilson
2018-04-03 12:38 ` [PATCH i-g-t v2] " Tvrtko Ursulin
2018-04-03 12:38   ` [Intel-gfx] " Tvrtko Ursulin
2018-04-03 13:10   ` Chris Wilson
2018-04-03 13:10     ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-04-03 16:09     ` Tvrtko Ursulin
2018-04-03 16:09       ` [Intel-gfx] " Tvrtko Ursulin
2018-04-03 16:24       ` Chris Wilson
2018-04-03 16:24         ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-04-03 16:39   ` [PATCH i-g-t v3] " Tvrtko Ursulin
2018-04-03 16:39     ` [igt-dev] " Tvrtko Ursulin
2018-04-04  9:51     ` [PATCH i-g-t v4] " Tvrtko Ursulin
2018-04-04  9:51       ` [Intel-gfx] " Tvrtko Ursulin
2018-04-11 13:23       ` Chris Wilson
2018-04-11 13:23         ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-04-11 13:52         ` Tvrtko Ursulin
2018-04-11 13:52           ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-04-14 11:35           ` Chris Wilson
2018-04-14 11:35             ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-04-16  9:55             ` Tvrtko Ursulin
2018-04-16  9:55               ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-04-16 10:08               ` Chris Wilson
2018-04-16 10:08                 ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-04-03 14:23 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf_pmu: Avoid RT thread for accuracy test (rev2) Patchwork
2018-04-03 16:41 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-04-03 17:15 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf_pmu: Avoid RT thread for accuracy test (rev3) Patchwork
2018-04-03 18:33 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-04-04 11:13   ` Tvrtko Ursulin
2018-04-04 13:46 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf_pmu: Avoid RT thread for accuracy test (rev4) Patchwork
2018-04-04 16:58 ` [igt-dev] ✓ 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=20180326130415.7436.37351@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=igt-dev@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 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.