From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/6] drm/i915/gt: Always enable busy-stats for execlists
Date: Wed, 29 Apr 2020 11:32:23 -0000 [thread overview]
Message-ID: <158815994368.6697.3989599444430290632@emeril.freedesktop.org> (raw)
In-Reply-To: <20200429103535.27781-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [CI,1/6] drm/i915/gt: Always enable busy-stats for execlists
URL : https://patchwork.freedesktop.org/series/76715/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8390 -> Patchwork_17508
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17508/index.html
Known issues
------------
Here are the changes found in Patchwork_17508 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@active:
- fi-kbl-x1275: [PASS][1] -> [DMESG-FAIL][2] ([i915#666])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8390/fi-kbl-x1275/igt@i915_selftest@live@active.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17508/fi-kbl-x1275/igt@i915_selftest@live@active.html
[i915#666]: https://gitlab.freedesktop.org/drm/intel/issues/666
Participating hosts (48 -> 41)
------------------------------
Missing (7): fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-kbl-7500u fi-ctg-p8600 fi-kbl-7560u fi-byt-clapper
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8390 -> Patchwork_17508
CI-20190529: 20190529
CI_DRM_8390: 89473e10666c78c4df9e92c9caf03d7311c291cb @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5614: d095827add11d4e8158b87683971ee659749d9a4 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17508: f62efbcbf8a78af6c2ab2a74a9d0baa598358a3f @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
f62efbcbf8a7 drm/i915/gt: Restore aggressive post-boost downclocking
c45bc814fafd drm/i915/gt: Apply the aggressive downclocking to parking
d663447ef62f drm/i915/gt: Switch to manual evaluation of RPS
f24bbcfa0789 drm/i915/gt: Track use of RPS interrupts in flags
1a3beaa34731 drm/i915/gt: Move rps.enabled/active to flags
081418e7ad56 drm/i915/gt: Always enable busy-stats for execlists
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17508/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-29 11:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 10:35 [Intel-gfx] [CI 1/6] drm/i915/gt: Always enable busy-stats for execlists Chris Wilson
2020-04-29 10:35 ` [Intel-gfx] [CI 2/6] drm/i915/gt: Move rps.enabled/active to flags Chris Wilson
2020-04-29 10:35 ` [Intel-gfx] [CI 3/6] drm/i915/gt: Track use of RPS interrupts in flags Chris Wilson
2020-04-29 10:35 ` [Intel-gfx] [CI 4/6] drm/i915/gt: Switch to manual evaluation of RPS Chris Wilson
2020-04-29 10:35 ` [Intel-gfx] [CI 5/6] drm/i915/gt: Apply the aggressive downclocking to parking Chris Wilson
2020-04-29 10:35 ` [Intel-gfx] [CI 6/6] drm/i915/gt: Restore aggressive post-boost downclocking Chris Wilson
2020-04-29 11:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/6] drm/i915/gt: Always enable busy-stats for execlists Patchwork
2020-04-29 11:32 ` Patchwork [this message]
2020-04-29 14:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-04-29 20:54 [Intel-gfx] [CI 1/6] " Chris Wilson
2020-04-29 22:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/6] " Patchwork
2020-04-28 21:31 [Intel-gfx] [CI 1/6] " Chris Wilson
2020-04-28 23:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/6] " 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=158815994368.6697.3989599444430290632@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 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.