From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.IGT: failure for igt/gem_eio: Preserve batch between reset-stress iterations
Date: Wed, 08 Aug 2018 18:15:33 -0000 [thread overview]
Message-ID: <20180808181533.2291.39232@emeril.freedesktop.org> (raw)
In-Reply-To: <20180808113137.3747-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: igt/gem_eio: Preserve batch between reset-stress iterations
URL : https://patchwork.freedesktop.org/series/47882/
State : failure
== Summary ==
= CI Bug Log - changes from IGT_4588_full -> IGTPW_1692_full =
== Summary - FAILURE ==
Serious unknown changes coming with IGTPW_1692_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_1692_full, 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/47882/revisions/1/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in IGTPW_1692_full:
=== IGT changes ===
==== Possible regressions ====
igt@gem_eio@reset-stress:
shard-snb: PASS -> FAIL
igt@gem_eio@wait-10ms:
shard-hsw: PASS -> FAIL
==== Warnings ====
igt@perf_pmu@rc6:
shard-kbl: PASS -> SKIP
== Known issues ==
Here are the changes found in IGTPW_1692_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_exec_await@wide-contexts:
shard-apl: PASS -> FAIL (fdo#105900, fdo#106680)
igt@gem_workarounds@suspend-resume-fd:
shard-kbl: PASS -> INCOMPLETE (fdo#103665) +1
igt@kms_cursor_legacy@pipe-b-torture-move:
shard-snb: PASS -> DMESG-WARN (fdo#107122)
igt@kms_flip@2x-flip-vs-expired-vblank:
shard-glk: PASS -> FAIL (fdo#105363)
igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-pwrite:
shard-glk: PASS -> FAIL (fdo#103167)
igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt:
shard-snb: PASS -> INCOMPLETE (fdo#105411)
igt@kms_rotation_crc@primary-rotation-180:
shard-snb: PASS -> FAIL (fdo#103925)
igt@kms_vblank@pipe-c-ts-continuation-idle-hang:
shard-apl: PASS -> DMESG-WARN (fdo#106247)
igt@pm_rpm@gem-execbuf:
shard-glk: PASS -> FAIL (fdo#106539)
igt@pm_rpm@modeset-lpsp:
shard-glk: SKIP -> FAIL (fdo#106539)
igt@testdisplay:
shard-glk: PASS -> INCOMPLETE (k.org#198133, fdo#107093, fdo#103359)
==== Possible fixes ====
igt@drv_suspend@shrink:
shard-snb: INCOMPLETE (fdo#105411, fdo#106886) -> PASS
igt@gem_softpin@evict-snoop-interruptible:
shard-snb: INCOMPLETE (fdo#105411) -> SKIP
igt@kms_plane_multiple@atomic-pipe-a-tiling-x:
shard-snb: FAIL (fdo#103166) -> PASS
igt@kms_vblank@pipe-a-ts-continuation-modeset-rpm:
shard-apl: FAIL (fdo#106539) -> PASS +1
igt@pm_rpm@gem-pread:
shard-glk: WARN -> PASS
igt@pm_rpm@modeset-non-lpsp-stress:
shard-kbl: FAIL (fdo#106539) -> PASS +1
shard-hsw: FAIL (fdo#106539) -> PASS +1
shard-glk: FAIL (fdo#106539) -> PASS
fdo#103166 https://bugs.freedesktop.org/show_bug.cgi?id=103166
fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
fdo#103359 https://bugs.freedesktop.org/show_bug.cgi?id=103359
fdo#103665 https://bugs.freedesktop.org/show_bug.cgi?id=103665
fdo#103925 https://bugs.freedesktop.org/show_bug.cgi?id=103925
fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
fdo#105900 https://bugs.freedesktop.org/show_bug.cgi?id=105900
fdo#106247 https://bugs.freedesktop.org/show_bug.cgi?id=106247
fdo#106539 https://bugs.freedesktop.org/show_bug.cgi?id=106539
fdo#106680 https://bugs.freedesktop.org/show_bug.cgi?id=106680
fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
fdo#107093 https://bugs.freedesktop.org/show_bug.cgi?id=107093
fdo#107122 https://bugs.freedesktop.org/show_bug.cgi?id=107122
k.org#198133 https://bugzilla.kernel.org/show_bug.cgi?id=198133
== Participating hosts (5 -> 5) ==
No changes in participating hosts
== Build changes ==
* IGT: IGT_4588 -> IGTPW_1692
* Linux: CI_DRM_4632 -> CI_DRM_4633
CI_DRM_4632: 648e2ff1094eabf43613f41d4d719c1a1f555dbb @ git://anongit.freedesktop.org/gfx-ci/linux
CI_DRM_4633: ea6e3f703e4d234c9c8eaec6c533355c7454ecb6 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_1692: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1692/
IGT_4588: 7e5abbe4d9b2129bbbf02be77a70cad3da2ab941 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1692/shards.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2018-08-08 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 11:31 [igt-dev] [PATCH i-g-t] igt/gem_eio: Preserve batch between reset-stress iterations Chris Wilson
2018-08-08 11:31 ` Chris Wilson
2018-08-08 12:38 ` [igt-dev] " Tvrtko Ursulin
2018-08-08 12:38 ` Tvrtko Ursulin
2018-08-08 12:47 ` [igt-dev] " Chris Wilson
2018-08-08 12:47 ` Chris Wilson
2018-08-08 12:57 ` [Intel-gfx] " Tvrtko Ursulin
2018-08-08 12:57 ` Tvrtko Ursulin
2018-08-08 14:19 ` [igt-dev] " Chris Wilson
2018-08-08 14:19 ` Chris Wilson
2018-08-08 12:58 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-08-08 18:15 ` Patchwork [this message]
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=20180808181533.2291.39232@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@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 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.