From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for Per client engine busyness
Date: Mon, 12 Jul 2021 13:01:56 -0000 [thread overview]
Message-ID: <162609491638.23769.6766048964101582971@emeril.freedesktop.org> (raw)
In-Reply-To: <20210712121719.891536-1-tvrtko.ursulin@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 4660 bytes --]
== Series Details ==
Series: Per client engine busyness
URL : https://patchwork.freedesktop.org/series/92435/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10333 -> Patchwork_20573
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/index.html
Known issues
------------
Here are the changes found in Patchwork_20573 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_huc_copy@huc-copy:
- fi-tgl-y: NOTRUN -> [SKIP][1] ([i915#2190])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/fi-tgl-y/igt@gem_huc_copy@huc-copy.html
* igt@kms_chamelium@vga-edid-read:
- fi-tgl-y: NOTRUN -> [SKIP][2] ([fdo#111827]) +8 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/fi-tgl-y/igt@kms_chamelium@vga-edid-read.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-y: NOTRUN -> [SKIP][3] ([fdo#109285])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/fi-tgl-y/igt@kms_force_connector_basic@force-load-detect.html
* igt@prime_vgem@basic-userptr:
- fi-tgl-y: NOTRUN -> [SKIP][4] ([i915#3301])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/fi-tgl-y/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-tgl-y: NOTRUN -> [FAIL][5] ([i915#2722] / [i915#3744])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/fi-tgl-y/igt@runner@aborted.html
* igt@vgem_basic@unload:
- fi-tgl-y: NOTRUN -> [INCOMPLETE][6] ([i915#3744])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/fi-tgl-y/igt@vgem_basic@unload.html
#### Possible fixes ####
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-7500u: [FAIL][7] ([i915#3449]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10333/fi-kbl-7500u/igt@kms_chamelium@common-hpd-after-suspend.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/fi-kbl-7500u/igt@kms_chamelium@common-hpd-after-suspend.html
#### Warnings ####
* igt@runner@aborted:
- fi-kbl-soraka: [FAIL][9] ([i915#2722] / [i915#3363] / [i915#3744]) -> [FAIL][10] ([i915#1569] / [i915#192] / [i915#193] / [i915#194] / [i915#2426] / [i915#3363])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10333/fi-kbl-soraka/igt@runner@aborted.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/fi-kbl-soraka/igt@runner@aborted.html
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1569]: https://gitlab.freedesktop.org/drm/intel/issues/1569
[i915#192]: https://gitlab.freedesktop.org/drm/intel/issues/192
[i915#193]: https://gitlab.freedesktop.org/drm/intel/issues/193
[i915#194]: https://gitlab.freedesktop.org/drm/intel/issues/194
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426
[i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363
[i915#3449]: https://gitlab.freedesktop.org/drm/intel/issues/3449
[i915#3744]: https://gitlab.freedesktop.org/drm/intel/issues/3744
Participating hosts (39 -> 39)
------------------------------
Additional (1): fi-tgl-y
Missing (1): fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_10333 -> Patchwork_20573
CI-20190529: 20190529
CI_DRM_10333: 138708ec9f303e98fded4239cafa0577d1f47030 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6134: cd63c83e23789eb194d38b8d272247a88122f2f6 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20573: 1fe5f6f4bff5f22aa43c3096848a48e844b76b00 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
1fe5f6f4bff5 drm: Document fdinfo format specification
e43d1b5db399 drm/i915: Expose client engine utilisation via fdinfo
76b7c1579fce drm/i915: Track context current active time
726f6083cc01 drm/i915: Track all user contexts per client
db56ccda834e drm/i915: Track runtime spent in closed and unreachable GEM contexts
8563c5aeca1a drm/i915: Make GEM contexts track DRM clients
f7063d21a85d drm/i915: Update client name on context create
cd1de51f55b2 drm/i915: Explicitly track DRM clients
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20573/index.html
[-- Attachment #1.2: Type: text/html, Size: 5744 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-07-12 13:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 12:17 [PATCH 0/8] Per client engine busyness Tvrtko Ursulin
2021-07-12 12:17 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 12:17 ` [PATCH 1/8] drm/i915: Explicitly track DRM clients Tvrtko Ursulin
2021-07-12 12:17 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 14:42 ` Daniel Vetter
2021-07-12 14:42 ` [Intel-gfx] " Daniel Vetter
2021-07-12 15:51 ` Tvrtko Ursulin
2021-07-12 15:51 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 16:12 ` Daniel Vetter
2021-07-12 16:12 ` [Intel-gfx] " Daniel Vetter
2021-07-13 8:50 ` Tvrtko Ursulin
2021-07-13 8:50 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 12:17 ` [PATCH 2/8] drm/i915: Update client name on context create Tvrtko Ursulin
2021-07-12 12:17 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 12:17 ` [PATCH 3/8] drm/i915: Make GEM contexts track DRM clients Tvrtko Ursulin
2021-07-12 12:17 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 12:17 ` [PATCH 4/8] drm/i915: Track runtime spent in closed and unreachable GEM contexts Tvrtko Ursulin
2021-07-12 12:17 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 12:17 ` [PATCH 5/8] drm/i915: Track all user contexts per client Tvrtko Ursulin
2021-07-12 12:17 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 12:17 ` [PATCH 6/8] drm/i915: Track context current active time Tvrtko Ursulin
2021-07-12 12:17 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 12:17 ` [RFC 7/8] drm/i915: Expose client engine utilisation via fdinfo Tvrtko Ursulin
2021-07-12 12:17 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 12:17 ` [RFC 8/8] drm: Document fdinfo format specification Tvrtko Ursulin
2021-07-12 12:17 ` [Intel-gfx] " Tvrtko Ursulin
2021-07-12 12:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Per client engine busyness Patchwork
2021-07-12 12:37 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-07-12 12:40 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-07-12 13:01 ` Patchwork [this message]
2021-07-12 16:00 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-05-20 15:12 [RFC 0/7] " Tvrtko Ursulin
2021-05-20 16:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-05-13 10:59 [PATCH 0/7] " Tvrtko Ursulin
2021-05-13 11:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-09-14 13:12 [Intel-gfx] [PATCH 0/9] " Tvrtko Ursulin
2020-09-14 18:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-09-04 12:59 [Intel-gfx] [PATCH 0/9] " Tvrtko Ursulin
2020-09-04 14:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-04-15 10:11 [Intel-gfx] [PATCH 0/9] " Tvrtko Ursulin
2020-04-15 11:34 ` [Intel-gfx] ✓ 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=162609491638.23769.6766048964101582971@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 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.