From: Patchwork <patchwork@emeril.freedesktop.org>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [v4,1/2] drm/i915/guc: Limit number of scratch registers used for H2G
Date: Mon, 22 Oct 2018 11:20:32 -0000 [thread overview]
Message-ID: <20181022112032.28549.31005@emeril.freedesktop.org> (raw)
In-Reply-To: <20181019101725.14024-1-michal.wajdeczko@intel.com>
== Series Details ==
Series: series starting with [v4,1/2] drm/i915/guc: Limit number of scratch registers used for H2G
URL : https://patchwork.freedesktop.org/series/51249/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5015 -> Patchwork_10514 =
== Summary - FAILURE ==
Serious unknown changes coming with Patchwork_10514 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_10514, 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/51249/revisions/1/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_10514:
=== IGT changes ===
==== Possible regressions ====
igt@drv_selftest@live_execlists:
fi-skl-6700hq: PASS -> INCOMPLETE
igt@drv_selftest@live_gem:
fi-skl-6770hq: PASS -> DMESG-WARN
igt@drv_selftest@live_hangcheck:
fi-kbl-8809g: PASS -> INCOMPLETE
fi-cfl-s3: PASS -> INCOMPLETE
==== Warnings ====
igt@drv_selftest@live_guc:
fi-skl-6700hq: PASS -> SKIP
== Known issues ==
Here are the changes found in Patchwork_10514 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
fi-icl-u: PASS -> INCOMPLETE (fdo#107713)
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
fi-byt-clapper: PASS -> FAIL (fdo#103191, fdo#107362) +1
==== Possible fixes ====
igt@gem_exec_suspend@basic-s4-devices:
fi-blb-e6850: INCOMPLETE (fdo#107718) -> PASS
igt@kms_pipe_crc_basic@read-crc-pipe-a:
fi-byt-clapper: FAIL (fdo#107362) -> PASS
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107713 https://bugs.freedesktop.org/show_bug.cgi?id=107713
fdo#107718 https://bugs.freedesktop.org/show_bug.cgi?id=107718
== Participating hosts (52 -> 45) ==
Missing (7): fi-kbl-soraka fi-ilk-m540 fi-byt-squawks fi-icl-u2 fi-bsw-cyan fi-ctg-p8600 fi-skl-6600u
== Build changes ==
* Linux: CI_DRM_5015 -> Patchwork_10514
CI_DRM_5015: ec78bedc9006e9e56067eb6524bbd3064475a055 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4685: 78619fde4008424c472906041edb1d204e014f7c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10514: 9a4269f293b74a7a69e0d5ed4d036f8eeddd8151 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
9a4269f293b7 HAX: Enable GuC for CI
76797b445c4b drm/i915/guc: Limit number of scratch registers used for H2G
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10514/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-10-22 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 10:17 [PATCH v4 1/2] drm/i915/guc: Limit number of scratch registers used for H2G Michal Wajdeczko
2018-10-19 10:17 ` [PATCH v4 2/2] HAX: Enable GuC for CI Michal Wajdeczko
2018-11-05 0:23 ` [LKP] [HAX] ddc7f46e1c: drm:i915_gem_init_hw[i915]] kernel test robot
2018-10-22 11:20 ` Patchwork [this message]
2018-10-22 11:37 ` ✗ Fi.CI.BAT: failure for series starting with [v4,1/2] drm/i915/guc: Limit number of scratch registers used for H2G Chris Wilson
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=20181022112032.28549.31005@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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