From: Patchwork <patchwork@emeril.freedesktop.org>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/gen11: Allow usage of all GPIO pins (rev4)
Date: Sat, 17 Aug 2019 01:55:13 -0000 [thread overview]
Message-ID: <20190817015513.13759.79165@emeril.freedesktop.org> (raw)
In-Reply-To: <20190815163524.12304-1-matthew.d.roper@intel.com>
== Series Details ==
Series: drm/i915/gen11: Allow usage of all GPIO pins (rev4)
URL : https://patchwork.freedesktop.org/series/65261/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6723 -> Patchwork_14067
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14067/
Known issues
------------
Here are the changes found in Patchwork_14067 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_module_load@reload:
- fi-blb-e6850: [PASS][1] -> [INCOMPLETE][2] ([fdo#107718])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6723/fi-blb-e6850/igt@i915_module_load@reload.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14067/fi-blb-e6850/igt@i915_module_load@reload.html
#### Possible fixes ####
* igt@gem_exec_fence@basic-busy-default:
- fi-icl-u3: [DMESG-WARN][3] ([fdo#107724]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6723/fi-icl-u3/igt@gem_exec_fence@basic-busy-default.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14067/fi-icl-u3/igt@gem_exec_fence@basic-busy-default.html
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-hsw-4770: [SKIP][5] ([fdo#109271]) -> [PASS][6] +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6723/fi-hsw-4770/igt@i915_pm_rpm@basic-pci-d3-state.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14067/fi-hsw-4770/igt@i915_pm_rpm@basic-pci-d3-state.html
* igt@kms_busy@basic-flip-c:
- {fi-icl-u4}: [DMESG-WARN][7] ([fdo#105602]) -> [PASS][8] +5 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6723/fi-icl-u4/igt@kms_busy@basic-flip-c.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14067/fi-icl-u4/igt@kms_busy@basic-flip-c.html
* igt@kms_chamelium@hdmi-edid-read:
- {fi-icl-u4}: [FAIL][9] ([fdo#111045]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6723/fi-icl-u4/igt@kms_chamelium@hdmi-edid-read.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14067/fi-icl-u4/igt@kms_chamelium@hdmi-edid-read.html
#### Warnings ####
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-icl-u2: [FAIL][11] ([fdo#109483]) -> [FAIL][12] ([fdo#111407])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6723/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14067/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#102505]: https://bugs.freedesktop.org/show_bug.cgi?id=102505
[fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483
[fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
[fdo#111049]: https://bugs.freedesktop.org/show_bug.cgi?id=111049
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
Participating hosts (54 -> 45)
------------------------------
Missing (9): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-bsw-n3050 fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6723 -> Patchwork_14067
CI-20190529: 20190529
CI_DRM_6723: 3f85829ae2a124e54e39977748f2c85cd4be6b34 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5138: b9abe0bf6c478c4f6cac56bff286d6926ad8c0ab @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14067: 058bf5a4651d0a4d9b32d1cc8aed27ac38544ea2 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
058bf5a4651d drm/i915/gen11: Allow usage of all GPIO pins
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14067/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-17 1:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 16:35 [PATCH] drm/i915/gen11: Allow usage of all GPIO pins Matt Roper
2019-08-15 17:13 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-08-15 22:39 ` [PATCH] " Matt Roper
2019-08-16 19:50 ` Souza, Jose
2019-08-17 0:50 ` [PATCH v3] " Matt Roper
2019-08-22 23:25 ` Lucas De Marchi
2019-08-16 0:16 ` ✗ Fi.CI.BAT: failure for drm/i915/gen11: Allow usage of all GPIO pins (rev2) Patchwork
2019-08-16 23:06 ` ✗ Fi.CI.BAT: failure for drm/i915/gen11: Allow usage of all GPIO pins (rev3) Patchwork
2019-08-17 1:55 ` Patchwork [this message]
2019-08-17 21:30 ` ✓ Fi.CI.IGT: success for drm/i915/gen11: Allow usage of all GPIO pins (rev4) Patchwork
2019-08-19 14:53 ` Matt Roper
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=20190817015513.13759.79165@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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