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.BAT: success for test/gem_exec_schedule: Check each engine is an independent timeline
Date: Mon, 23 Apr 2018 15:32:30 -0000 [thread overview]
Message-ID: <20180423153230.5178.44150@emeril.freedesktop.org> (raw)
In-Reply-To: <20180423134345.28153-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: test/gem_exec_schedule: Check each engine is an independent timeline
URL : https://patchwork.freedesktop.org/series/42122/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4078 -> IGTPW_1292 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/42122/revisions/1/mbox/
== Known issues ==
Here are the changes found in IGTPW_1292 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_exec_suspend@basic-s4-devices:
fi-kbl-7500u: PASS -> DMESG-WARN (fdo#105128)
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
fi-ivb-3520m: PASS -> DMESG-WARN (fdo#106084)
==== Possible fixes ====
igt@gem_mmap_gtt@basic-small-bo-tiledx:
fi-gdg-551: FAIL (fdo#102575) -> PASS
fdo#102575 https://bugs.freedesktop.org/show_bug.cgi?id=102575
fdo#105128 https://bugs.freedesktop.org/show_bug.cgi?id=105128
fdo#106084 https://bugs.freedesktop.org/show_bug.cgi?id=106084
== Participating hosts (36 -> 33) ==
Missing (3): fi-ctg-p8600 fi-ilk-m540 fi-skl-6700hq
== Build changes ==
* IGT: IGT_4444 -> IGTPW_1292
CI_DRM_4078: 9391010824b34ec58217f816ba5e314e7312191d @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_1292: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1292/
IGT_4444: dcc44347494231feabc588c2a76998cbc9afdf8c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4444: a2f486679f467cd6e82578384f56d4aabaa8cf2e @ git://anongit.freedesktop.org/piglit
== Testlist changes ==
+igt@gem_exec_schedule@independent-blt
+igt@gem_exec_schedule@independent-bsd
+igt@gem_exec_schedule@independent-bsd1
+igt@gem_exec_schedule@independent-bsd2
+igt@gem_exec_schedule@independent-render
+igt@gem_exec_schedule@independent-vebox
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1292/issues.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-04-23 15:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 13:43 [PATCH igt] test/gem_exec_schedule: Check each engine is an independent timeline Chris Wilson
2018-04-23 13:43 ` [igt-dev] " Chris Wilson
2018-04-23 15:32 ` Patchwork [this message]
2018-04-23 15:37 ` Antonio Argenziano
2018-04-23 15:37 ` Antonio Argenziano
2018-04-23 15:51 ` Chris Wilson
2018-04-23 15:51 ` Chris Wilson
2018-04-23 16:00 ` Antonio Argenziano
2018-04-23 16:00 ` Antonio Argenziano
2018-04-23 16:52 ` Tvrtko Ursulin
2018-04-23 16:52 ` Tvrtko Ursulin
2018-04-23 17:08 ` Chris Wilson
2018-04-23 17:08 ` [Intel-gfx] " Chris Wilson
2018-04-24 8:55 ` Tvrtko Ursulin
2018-04-24 8:55 ` Tvrtko Ursulin
2018-04-24 9:23 ` Chris Wilson
2018-04-24 9:23 ` [Intel-gfx] " Chris Wilson
2018-04-23 18:22 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
2018-04-23 20:33 ` [PATCH igt v2] " Chris Wilson
2018-04-23 20:33 ` [igt-dev] " Chris Wilson
2018-04-23 23:16 ` [PATCH igt] " Chris Wilson
2018-04-23 23:16 ` [igt-dev] " Chris Wilson
2018-04-24 9:29 ` Tvrtko Ursulin
2018-04-24 9:29 ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-04-23 21:04 ` [igt-dev] ✓ Fi.CI.BAT: success for test/gem_exec_schedule: Check each engine is an independent timeline (rev2) Patchwork
2018-04-23 22:20 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-04-24 0:30 ` [igt-dev] ✓ Fi.CI.BAT: success for test/gem_exec_schedule: Check each engine is an independent timeline (rev3) Patchwork
2018-04-24 1:30 ` [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=20180423153230.5178.44150@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.