From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for Per context dynamic (sub)slice power-gating (rev12)
Date: Tue, 08 Jan 2019 19:00:14 -0000 [thread overview]
Message-ID: <20190108190014.28500.81458@emeril.freedesktop.org> (raw)
In-Reply-To: <20190108151252.4214-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: Per context dynamic (sub)slice power-gating (rev12)
URL : https://patchwork.freedesktop.org/series/48194/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5379 -> Patchwork_11256
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with Patchwork_11256 need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_11256, 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/48194/revisions/12/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_11256:
### IGT changes ###
#### Warnings ####
* igt@pm_rpm@basic-pci-d3-state:
- fi-byt-j1900: SKIP -> PASS
Known issues
------------
Here are the changes found in Patchwork_11256 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-kbl-7567u: PASS -> INCOMPLETE [fdo#103665]
#### Possible fixes ####
* igt@gem_exec_basic@gtt-bsd2:
- fi-skl-6770hq: DMESG-WARN [fdo#105541] -> PASS
* igt@i915_selftest@live_execlists:
- fi-apl-guc: INCOMPLETE [fdo#103927] -> PASS
* igt@i915_selftest@live_hangcheck:
- fi-bwr-2160: DMESG-FAIL [fdo#108735] -> PASS
* igt@kms_frontbuffer_tracking@basic:
- fi-hsw-peppy: DMESG-WARN [fdo#102614] -> PASS
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-byt-clapper: FAIL [fdo#103191] / [fdo#107362] -> PASS
* igt@pm_rpm@basic-rte:
- fi-byt-j1900: FAIL [fdo#108800] -> PASS
[fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#105541]: https://bugs.freedesktop.org/show_bug.cgi?id=105541
[fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
[fdo#108735]: https://bugs.freedesktop.org/show_bug.cgi?id=108735
[fdo#108800]: https://bugs.freedesktop.org/show_bug.cgi?id=108800
Participating hosts (49 -> 45)
------------------------------
Missing (4): fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_5379 -> Patchwork_11256
CI_DRM_5379: cae04ddb2142baf68abdf7855e28c00a34b721b7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4756: 75081c6bfb9998bd7cbf35a7ac0578c683fe55a8 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_11256: 625fca5d7b43de1374e10cebeffd5a354cb57180 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
625fca5d7b43 drm/i915/selftests: Context SSEU reconfiguration tests
509b28e8038e drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only)
823fb1c4bf8f drm/i915: Add timeline barrier support
557c7dad1ad9 drm/i915/perf: lock powergating configuration to default when active
65954284c0af drm/i915: Record the sseu configuration per-context & engine
c919f2ba4d24 drm/i915/execlists: Move RPCS setup to context pin
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11256/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-08 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 15:12 [PATCH 0/6] Per context dynamic (sub)slice power-gating Tvrtko Ursulin
2019-01-08 15:12 ` [PATCH 1/6] drm/i915/execlists: Move RPCS setup to context pin Tvrtko Ursulin
2019-01-08 15:12 ` [PATCH 2/6] drm/i915: Record the sseu configuration per-context & engine Tvrtko Ursulin
2019-01-08 15:12 ` [PATCH 3/6] drm/i915/perf: lock powergating configuration to default when active Tvrtko Ursulin
2019-01-08 15:12 ` [PATCH 4/6] drm/i915: Add timeline barrier support Tvrtko Ursulin
2019-01-08 15:12 ` [PATCH 5/6] drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only) Tvrtko Ursulin
2019-01-08 16:29 ` [PATCH v24 " Tvrtko Ursulin
2019-01-11 14:22 ` Tvrtko Ursulin
2019-01-14 9:39 ` [PATCH v25 " Tvrtko Ursulin
2019-01-08 15:12 ` [PATCH 6/6] drm/i915/selftests: Context SSEU reconfiguration tests Tvrtko Ursulin
2019-01-08 15:37 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev11) Patchwork
2019-01-08 15:40 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-08 16:13 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-08 18:38 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev12) Patchwork
2019-01-08 18:40 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-08 19:00 ` Patchwork [this message]
2019-01-09 8:12 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-01-14 12:32 ` ✗ Fi.CI.BAT: failure for Per context dynamic (sub)slice power-gating (rev13) 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=20190108190014.28500.81458@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.intel.com \
/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