From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for series starting with [CI,1/5] drm/i915: Stop tracking MRU activity on VMA
Date: Mon, 28 Jan 2019 16:21:25 -0000 [thread overview]
Message-ID: <20190128162125.32722.41780@emeril.freedesktop.org> (raw)
In-Reply-To: <20190128102356.15037-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [CI,1/5] drm/i915: Stop tracking MRU activity on VMA
URL : https://patchwork.freedesktop.org/series/55829/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5494 -> Patchwork_12057
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/55829/revisions/1/mbox/
Known issues
------------
Here are the changes found in Patchwork_12057 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:
- fi-byt-clapper: PASS -> FAIL [fdo#103191] / [fdo#107362] +1
* igt@pm_rpm@module-reload:
- fi-skl-6770hq: PASS -> FAIL [fdo#108511]
#### Possible fixes ####
* igt@kms_busy@basic-flip-b:
- fi-gdg-551: FAIL [fdo#103182] -> PASS
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-7567u: WARN [fdo#109380] -> PASS
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-c:
- fi-kbl-7567u: {SKIP} [fdo#109271] -> PASS +33
{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#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109380]: https://bugs.freedesktop.org/show_bug.cgi?id=109380
Participating hosts (43 -> 38)
------------------------------
Additional (1): fi-skl-6700hq
Missing (6): fi-kbl-soraka fi-ilk-m540 fi-byt-j1900 fi-bsw-cyan fi-pnv-d510 fi-icl-y
Build changes
-------------
* Linux: CI_DRM_5494 -> Patchwork_12057
CI_DRM_5494: 543c074ff6a401b2bca5333234a9c13c4b0a5152 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4795: 031715e369cf01aecbe293910211e80e51995ffb @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12057: 58651f8391777c88dccd46da5a609a7e4b636e16 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
58651f839177 drm/i915: Move list of timelines under its own lock
2a803627cd9e drm/i915: Always allocate an object/vma for the HWSP
3c6c66d230a5 drm/i915: Move vma lookup to its own lock
61fb9c56e8df drm/i915: Pull VM lists under the VM mutex.
6c5b3f15bc23 drm/i915: Stop tracking MRU activity on VMA
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12057/
_______________________________________________
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-28 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 10:23 [CI 1/5] drm/i915: Stop tracking MRU activity on VMA Chris Wilson
2019-01-28 10:23 ` [CI 2/5] drm/i915: Pull VM lists under the VM mutex Chris Wilson
2019-01-28 10:23 ` [CI 3/5] drm/i915: Move vma lookup to its own lock Chris Wilson
2019-01-28 10:23 ` [CI 4/5] drm/i915: Always allocate an object/vma for the HWSP Chris Wilson
2019-01-28 10:23 ` [CI 5/5] drm/i915: Move list of timelines under its own lock Chris Wilson
2019-01-28 14:54 ` ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/5] drm/i915: Stop tracking MRU activity on VMA Patchwork
2019-01-28 16:21 ` Patchwork [this message]
2019-01-28 20:12 ` ✓ Fi.CI.IGT: success " 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=20190128162125.32722.41780@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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