From: Patchwork <patchwork@emeril.freedesktop.org>
To: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for GuC suspend paths cleanup
Date: Wed, 20 Feb 2019 02:34:51 -0000 [thread overview]
Message-ID: <20190220023451.5011.1504@emeril.freedesktop.org> (raw)
In-Reply-To: <20190220013927.9488-1-sujaritha.sundaresan@intel.com>
== Series Details ==
Series: GuC suspend paths cleanup
URL : https://patchwork.freedesktop.org/series/56938/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5633 -> Patchwork_12262
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/56938/revisions/1/mbox/
Known issues
------------
Here are the changes found in Patchwork_12262 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s4-devices:
- fi-blb-e6850: PASS -> INCOMPLETE [fdo#107718]
* igt@kms_pipe_crc_basic@hang-read-crc-pipe-b:
- fi-byt-clapper: PASS -> FAIL [fdo#103191] / [fdo#107362]
* igt@pm_rpm@basic-rte:
- fi-bsw-kefka: NOTRUN -> FAIL [fdo#108800]
#### Possible fixes ####
* igt@kms_busy@basic-flip-a:
- fi-gdg-551: FAIL [fdo#103182] -> PASS
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-byt-clapper: FAIL [fdo#103191] / [fdo#107362] -> PASS +1
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103182]: https://bugs.freedesktop.org/show_bug.cgi?id=103182
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#108800]: https://bugs.freedesktop.org/show_bug.cgi?id=108800
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
Participating hosts (43 -> 41)
------------------------------
Additional (2): fi-bsw-kefka fi-pnv-d510
Missing (4): fi-kbl-soraka fi-ilk-m540 fi-byt-squawks fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_5633 -> Patchwork_12262
CI_DRM_5633: e507167d9a057512937d8944566f817c071c8443 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4840: c12b1f87adc4c568b21cc6ed9076b94bea46b010 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12262: 16533d032f4fb9aa7cfc2f30879128f73f6a3a94 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
16533d032f4f drm/i915/guc: Calling guc_disable_communication in all suspend paths
87b2a8a5132c drm/i915/guc: Splitting CT channel open/close functions
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12262/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-20 2:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 1:39 [PATCH v3 0/2] GuC suspend paths cleanup Sujaritha Sundaresan
2019-02-20 1:39 ` [PATCH v3 1/2] drm/i915/guc: Splitting CT channel open/close functions Sujaritha Sundaresan
2019-02-20 16:51 ` Daniele Ceraolo Spurio
2019-02-21 0:54 ` Chris Wilson
2019-02-20 1:39 ` [PATCH v3 2/2] drm/i915/guc: Calling guc_disable_communication in all suspend paths Sujaritha Sundaresan
2019-02-20 2:09 ` ✗ Fi.CI.CHECKPATCH: warning for GuC suspend paths cleanup Patchwork
2019-02-20 2:34 ` Patchwork [this message]
2019-02-20 4:55 ` ✓ Fi.CI.IGT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-02-14 21:45 [PATCH 0/2] " Sujaritha Sundaresan
2019-02-14 23:32 ` ✓ Fi.CI.BAT: success for " 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=20190220023451.5011.1504@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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