From: Patchwork <patchwork@emeril.freedesktop.org>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915: Verify power domains after enabling them (rev2)
Date: Fri, 17 Aug 2018 13:44:57 -0000 [thread overview]
Message-ID: <20180817134457.21066.14660@emeril.freedesktop.org> (raw)
In-Reply-To: <20180817122613.5449-1-imre.deak@intel.com>
== Series Details ==
Series: drm/i915: Verify power domains after enabling them (rev2)
URL : https://patchwork.freedesktop.org/series/48394/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4685 -> Patchwork_9971 =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwork_9971 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_9971, 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/48394/revisions/2/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_9971:
=== IGT changes ===
==== Possible regressions ====
igt@gem_exec_suspend@basic-s3:
fi-skl-6770hq: PASS -> DMESG-WARN +3
{fi-cfl-8109u}: PASS -> DMESG-WARN +3
fi-cfl-s3: PASS -> DMESG-WARN +3
fi-skl-6260u: PASS -> DMESG-WARN +3
fi-kbl-7567u: PASS -> DMESG-WARN +3
fi-kbl-guc: PASS -> DMESG-WARN
{fi-kbl-8809g}: PASS -> DMESG-WARN
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
fi-whl-u: PASS -> DMESG-WARN +3
fi-cfl-guc: PASS -> DMESG-WARN +3
fi-glk-j4005: PASS -> DMESG-WARN +3
fi-kbl-7500u: PASS -> DMESG-WARN +3
fi-kbl-7560u: PASS -> DMESG-WARN +3
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
{fi-skl-iommu}: PASS -> DMESG-WARN +3
fi-skl-6700k2: PASS -> DMESG-WARN +4
fi-skl-6700hq: PASS -> DMESG-WARN +3
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
fi-glk-dsi: PASS -> DMESG-WARN +3
fi-cfl-8700k: PASS -> DMESG-WARN +3
fi-skl-guc: PASS -> DMESG-WARN +3
fi-bxt-j4205: PASS -> DMESG-WARN +3
fi-bxt-dsi: PASS -> DMESG-WARN +3
fi-cnl-psr: PASS -> DMESG-WARN +3
fi-skl-gvtdvm: PASS -> DMESG-WARN +3
fi-skl-6600u: PASS -> DMESG-WARN +3
==== Warnings ====
{igt@pm_rpm@module-reload}:
{fi-icl-u}: WARN (fdo#107602) -> DMESG-FAIL
== Known issues ==
Here are the changes found in Patchwork_9971 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@drv_selftest@live_guc:
{fi-icl-u}: PASS -> DMESG-WARN (fdo#107591) +14
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
{fi-icl-u}: PASS -> DMESG-WARN (fdo#107382) +3
{igt@pm_rpm@module-reload}:
fi-byt-j1900: NOTRUN -> WARN (fdo#107602)
==== Possible fixes ====
igt@gem_exec_basic@readonly-blt:
fi-byt-n2820: FAIL (fdo#105900) -> PASS
igt@kms_frontbuffer_tracking@basic:
fi-hsw-peppy: DMESG-FAIL (fdo#102614) -> PASS
igt@prime_vgem@basic-fence-flip:
fi-ivb-3770: FAIL (fdo#104008) -> PASS
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614
fdo#104008 https://bugs.freedesktop.org/show_bug.cgi?id=104008
fdo#105900 https://bugs.freedesktop.org/show_bug.cgi?id=105900
fdo#107382 https://bugs.freedesktop.org/show_bug.cgi?id=107382
fdo#107591 https://bugs.freedesktop.org/show_bug.cgi?id=107591
fdo#107602 https://bugs.freedesktop.org/show_bug.cgi?id=107602
== Participating hosts (52 -> 49) ==
Additional (1): fi-byt-j1900
Missing (4): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-hsw-4200u
== Build changes ==
* Linux: CI_DRM_4685 -> Patchwork_9971
CI_DRM_4685: df7e8eddc3830216d3fec15e2c7d0b6ec97e7bae @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4606: 38a44003774e35c587c67c8766b35e75dbb993b8 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9971: 3f95a53c8ade0421b75908a68a0dad7a3e6d106c @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
3f95a53c8ade drm/i915: Verify power domains after enabling them
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9971/issues.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-08-17 13:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 12:26 [PATCH] drm/i915: Verify power domains after enabling them Imre Deak
2018-08-17 12:32 ` Chris Wilson
2018-08-17 12:53 ` Imre Deak
2018-08-17 12:58 ` Chris Wilson
2018-08-17 12:51 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-08-17 13:09 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-17 13:18 ` [PATCH v2] " Imre Deak
2018-08-17 13:25 ` Chris Wilson
2018-08-17 14:58 ` [PATCH v3] " Imre Deak
2018-08-17 15:28 ` Chris Wilson
2018-08-17 13:27 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Verify power domains after enabling them (rev2) Patchwork
2018-08-17 13:44 ` Patchwork [this message]
2018-08-17 13:56 ` ✗ Fi.CI.BAT: failure " Imre Deak
2018-08-17 13:57 ` Chris Wilson
2018-08-17 15:07 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Verify power domains after enabling them (rev3) Patchwork
2018-08-17 15:24 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-20 9:20 ` Imre Deak
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=20180817134457.21066.14660@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=imre.deak@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).