From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ Fi.CI.BAT: success for Test all YCbCr encodings/ranges (rev3)
Date: Tue, 02 Jul 2019 18:28:31 -0000 [thread overview]
Message-ID: <20190702182831.28691.10605@emeril.freedesktop.org> (raw)
In-Reply-To: <20190628194438.2714-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: Test all YCbCr encodings/ranges (rev3)
URL : https://patchwork.freedesktop.org/series/62963/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6396 -> IGTPW_3227
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/62963/revisions/3/mbox/
Known issues
------------
Here are the changes found in IGTPW_3227 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_cpu_reloc@basic:
- fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6396/fi-icl-u3/igt@gem_cpu_reloc@basic.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3227/fi-icl-u3/igt@gem_cpu_reloc@basic.html
* igt@i915_module_load@reload:
- fi-blb-e6850: [PASS][3] -> [INCOMPLETE][4] ([fdo#107718])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6396/fi-blb-e6850/igt@i915_module_load@reload.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3227/fi-blb-e6850/igt@i915_module_load@reload.html
* igt@i915_pm_rpm@module-reload:
- fi-kbl-r: [PASS][5] -> [DMESG-WARN][6] ([fdo#111012])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6396/fi-kbl-r/igt@i915_pm_rpm@module-reload.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3227/fi-kbl-r/igt@i915_pm_rpm@module-reload.html
#### Possible fixes ####
* igt@gem_basic@create-close:
- fi-icl-u3: [DMESG-WARN][7] ([fdo#107724]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6396/fi-icl-u3/igt@gem_basic@create-close.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3227/fi-icl-u3/igt@gem_basic@create-close.html
* igt@gem_ctx_create@basic-files:
- fi-icl-dsi: [INCOMPLETE][9] ([fdo#107713] / [fdo#109100]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6396/fi-icl-dsi/igt@gem_ctx_create@basic-files.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3227/fi-icl-dsi/igt@gem_ctx_create@basic-files.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][11] ([fdo#109485]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6396/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3227/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#109100]: https://bugs.freedesktop.org/show_bug.cgi?id=109100
[fdo#109485]: https://bugs.freedesktop.org/show_bug.cgi?id=109485
[fdo#111012]: https://bugs.freedesktop.org/show_bug.cgi?id=111012
Participating hosts (56 -> 47)
------------------------------
Missing (9): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* IGT: IGT_5079 -> IGTPW_3227
CI_DRM_6396: f6747e7cc19107131922db8fdeabc6c09d812300 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3227: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3227/
IGT_5079: 873df2fa9e8f5fd02d4532b30ef2579f4fe4f27f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3227/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-07-02 18:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 19:44 [igt-dev] [PATCH i-g-t 0/3] Test all YCbCr encodings/ranges Ville Syrjala
2019-06-28 19:44 ` [igt-dev] [PATCH i-g-t 1/3] lib/igt_fb: Allow creating yuv fbs with different encodings/ranges Ville Syrjala
2019-07-02 14:47 ` Shankar, Uma
2019-07-02 17:56 ` [igt-dev] [PATCH i-g-t v2 " Ville Syrjala
2019-06-28 19:44 ` [igt-dev] [PATCH i-g-t 2/3] tests/kms_plane: Test all YCbCr encodings/ranges Ville Syrjala
2019-07-02 15:09 ` Shankar, Uma
2019-07-02 17:57 ` [igt-dev] [PATCH i-g-t v2 " Ville Syrjala
2019-07-02 18:07 ` Kazlauskas, Nicholas
2019-07-03 17:12 ` Ville Syrjälä
2019-07-03 18:01 ` Kazlauskas, Nicholas
2019-06-28 19:44 ` [igt-dev] [PATCH i-g-t 3/3] tests/kms_plane: Throw away yet another bi Ville Syrjala
2019-07-02 13:20 ` Kazlauskas, Nicholas
2019-07-02 13:30 ` Ville Syrjälä
2019-07-02 16:44 ` Shankar, Uma
2019-07-02 17:04 ` Ville Syrjälä
2019-07-03 12:41 ` Shankar, Uma
2019-06-28 22:48 ` [igt-dev] ✓ Fi.CI.BAT: success for Test all YCbCr encodings/ranges Patchwork
2019-06-29 9:45 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-07-02 17:57 ` [igt-dev] ✗ Fi.CI.BAT: failure for Test all YCbCr encodings/ranges (rev2) Patchwork
2019-07-02 18:08 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2019-07-02 18:28 ` Patchwork [this message]
2019-07-03 16:53 ` [igt-dev] ✗ Fi.CI.IGT: failure for Test all YCbCr encodings/ranges (rev3) 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=20190702182831.28691.10605@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox