From: Patchwork <patchwork@emeril.freedesktop.org>
To: Uma Shankar <uma.shankar@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_color: Fix CRC mismatch issues with ctm test (rev4)
Date: Mon, 25 Mar 2019 08:49:02 -0000 [thread overview]
Message-ID: <20190325084902.10662.16608@emeril.freedesktop.org> (raw)
In-Reply-To: <1553503242-12020-1-git-send-email-uma.shankar@intel.com>
== Series Details ==
Series: tests/kms_color: Fix CRC mismatch issues with ctm test (rev4)
URL : https://patchwork.freedesktop.org/series/58412/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5808 -> IGTPW_2698
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_2698 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_2698, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://patchwork.freedesktop.org/api/1.0/series/58412/revisions/4/mbox/
Changes
-------
No changes found
Participating hosts (36 -> 5)
------------------------------
ERROR: It appears as if the changes made in IGTPW_2698 prevented too many machines from booting.
Missing (31): fi-skl-6770hq fi-bdw-gvtdvm fi-snb-2520m fi-apl-guc fi-bxt-j4205 fi-icl-u3 fi-pnv-d510 fi-skl-lmem fi-blb-e6850 fi-byt-n2820 fi-skl-6600u fi-hsw-4770r fi-bxt-dsi fi-bwr-2160 fi-ilk-650 fi-kbl-7500u fi-hsw-4770 fi-ivb-3770 fi-skl-6700k2 fi-kbl-7567u fi-ilk-m540 fi-skl-gvtdvm fi-skl-guc fi-cfl-8700k fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-whl-u fi-cfl-8109u fi-skl-iommu fi-kbl-8809g
Build changes
-------------
* IGT: IGT_4902 -> IGTPW_2698
CI_DRM_5808: 0053882c75f979b475f4d543c4b14cbbed218f38 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_2698: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2698/
IGT_4902: 3d325bb211d8cd84c6862c9945185a937395cb44 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2698/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-25 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 8:40 [igt-dev] [v3] tests/kms_color: Fix CRC mismatch issues with ctm test Uma Shankar
2019-03-25 8:49 ` Patchwork [this message]
2019-03-25 14:27 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_color: Fix CRC mismatch issues with ctm test (rev5) Patchwork
2019-03-26 9:51 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_color: Fix CRC mismatch issues with ctm test (rev6) Patchwork
2019-03-26 10:31 ` [igt-dev] [v3] tests/kms_color: Fix CRC mismatch issues with ctm test Shankar, Uma
2019-03-26 16:46 ` Ville Syrjälä
2019-03-27 6:20 ` Shankar, Uma
2019-03-27 10:36 ` Ville Syrjälä
2019-03-27 10:52 ` Shankar, Uma
2019-03-27 11:35 ` Ville Syrjälä
2019-03-27 13:37 ` Shankar, Uma
2019-03-28 19:38 ` Ville Syrjälä
2019-03-28 19:53 ` Shankar, Uma
2019-03-28 20:50 ` Shankar, Uma
2019-03-26 12:34 ` [igt-dev] ✓ Fi.CI.IGT: success for tests/kms_color: Fix CRC mismatch issues with ctm test (rev6) 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=20190325084902.10662.16608@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=uma.shankar@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