From: Patchwork <patchwork@emeril.freedesktop.org>
To: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915: Restore interrupt enabling after a reset (rev2)
Date: Sat, 16 Feb 2019 00:11:03 -0000 [thread overview]
Message-ID: <20190216001103.7912.76850@emeril.freedesktop.org> (raw)
In-Reply-To: <20190215220355.26146-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Restore interrupt enabling after a reset (rev2)
URL : https://patchwork.freedesktop.org/series/56761/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5612 -> Patchwork_12231
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_12231 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_12231, 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/56761/revisions/2/mbox/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_12231:
### IGT changes ###
#### Possible regressions ####
* igt@i915_hangman@error-state-basic:
- fi-bwr-2160: PASS -> INCOMPLETE
- fi-hsw-4770r: PASS -> DMESG-WARN
- fi-ivb-3770: PASS -> DMESG-WARN
- fi-hsw-4770: PASS -> DMESG-WARN
- fi-snb-2520m: PASS -> DMESG-WARN
- fi-pnv-d510: PASS -> INCOMPLETE
- fi-ilk-650: PASS -> DMESG-WARN
- fi-snb-2600: PASS -> DMESG-WARN
- fi-ivb-3520m: PASS -> DMESG-WARN
* igt@i915_selftest@live_workarounds:
- fi-bsw-n3050: PASS -> INCOMPLETE
- fi-skl-6700hq: PASS -> DMESG-WARN
- fi-bsw-kefka: PASS -> INCOMPLETE
- fi-kbl-7500u: PASS -> DMESG-WARN
- fi-cfl-8109u: PASS -> DMESG-WARN
- fi-skl-6600u: PASS -> DMESG-WARN
- fi-kbl-7560u: PASS -> DMESG-WARN
- fi-bdw-5557u: PASS -> DMESG-WARN
- fi-kbl-7567u: PASS -> DMESG-WARN
- fi-skl-6700k2: PASS -> DMESG-WARN
- fi-skl-iommu: PASS -> DMESG-WARN
- fi-skl-6770hq: PASS -> DMESG-WARN
- fi-kbl-x1275: PASS -> DMESG-WARN
- fi-skl-6260u: PASS -> DMESG-WARN
- fi-kbl-r: PASS -> DMESG-WARN
- fi-skl-gvtdvm: PASS -> DMESG-WARN
- fi-bdw-gvtdvm: PASS -> DMESG-WARN
- fi-cfl-8700k: PASS -> DMESG-WARN
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@i915_selftest@live_workarounds:
- {fi-icl-y}: PASS -> DMESG-WARN
- {fi-whl-u}: PASS -> DMESG-WARN
- {fi-icl-u3}: PASS -> DMESG-WARN
- {fi-icl-u2}: PASS -> DMESG-WARN
* {igt@runner@aborted}:
- fi-ilk-650: NOTRUN -> FAIL
- fi-bdw-gvtdvm: NOTRUN -> FAIL
- fi-cfl-8109u: NOTRUN -> FAIL
- {fi-icl-u2}: NOTRUN -> FAIL
- fi-snb-2520m: NOTRUN -> FAIL
- fi-hsw-4770: NOTRUN -> FAIL
- fi-kbl-7500u: NOTRUN -> FAIL
- {fi-whl-u}: NOTRUN -> FAIL
- {fi-icl-u3}: NOTRUN -> FAIL
- fi-ivb-3770: NOTRUN -> FAIL
- fi-kbl-7560u: NOTRUN -> FAIL
- {fi-icl-y}: NOTRUN -> FAIL
- fi-kbl-7567u: NOTRUN -> FAIL
- fi-kbl-x1275: NOTRUN -> FAIL
- fi-cfl-8700k: NOTRUN -> FAIL
- fi-hsw-4770r: NOTRUN -> FAIL
- fi-kbl-r: NOTRUN -> FAIL
- fi-bdw-5557u: NOTRUN -> FAIL
- fi-ivb-3520m: NOTRUN -> FAIL
- fi-snb-2600: NOTRUN -> FAIL
Known issues
------------
Here are the changes found in Patchwork_12231 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@userptr:
- fi-kbl-8809g: PASS -> DMESG-WARN [fdo#108965]
* igt@gem_exec_suspend@basic-s3:
- fi-blb-e6850: PASS -> INCOMPLETE [fdo#107718]
* igt@i915_hangman@error-state-basic:
- fi-byt-n2820: PASS -> INCOMPLETE [fdo#102657]
- fi-byt-clapper: PASS -> INCOMPLETE [fdo#102657]
- fi-byt-j1900: PASS -> INCOMPLETE [fdo#102657]
- fi-elk-e7500: PASS -> INCOMPLETE [fdo#103989]
* igt@kms_flip@basic-flip-vs-modeset:
- fi-skl-6700hq: PASS -> DMESG-WARN [fdo#105998]
#### Possible fixes ####
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-7567u: WARN [fdo#109380] -> PASS
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-c:
- fi-kbl-7567u: {SKIP} [fdo#109271] -> PASS +33
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#102657]: https://bugs.freedesktop.org/show_bug.cgi?id=102657
[fdo#103989]: https://bugs.freedesktop.org/show_bug.cgi?id=103989
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#105998]: https://bugs.freedesktop.org/show_bug.cgi?id=105998
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#108622]: https://bugs.freedesktop.org/show_bug.cgi?id=108622
[fdo#108965]: https://bugs.freedesktop.org/show_bug.cgi?id=108965
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109380]: https://bugs.freedesktop.org/show_bug.cgi?id=109380
Participating hosts (45 -> 43)
------------------------------
Additional (1): fi-glk-j4005
Missing (3): fi-ilk-m540 fi-byt-squawks fi-bsw-cyan
Build changes
-------------
* Linux: CI_DRM_5612 -> Patchwork_12231
CI_DRM_5612: 6067ec567b3eda30cecc8e03b65c4783f8708a8c @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4832: 324ab48e67065f0cf67525b3ab9c44fd3dcaef0a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12231: 5c139f128392c62fe027d45b91431db36611a695 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
5c139f128392 drm/i915: Restore interrupt enabling after a reset
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12231/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-16 0:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 22:03 [PATCH] drm/i915: Restore interrupt enabling after a reset Chris Wilson
2019-02-15 22:30 ` [PATCH v2] " Chris Wilson
2019-02-15 23:42 ` [PATCH v3] " Chris Wilson
2019-02-16 0:11 ` Patchwork [this message]
2019-02-16 1:12 ` ✗ Fi.CI.BAT: failure for drm/i915: Restore interrupt enabling after a reset (rev3) Patchwork
2019-02-18 9:10 ` [PATCH] drm/i915: Restore interrupt enabling after a reset Chris Wilson
2019-02-18 10:36 ` ✓ Fi.CI.BAT: success for drm/i915: Restore interrupt enabling after a reset (rev4) Patchwork
2019-02-18 13:47 ` ✓ Fi.CI.IGT: " Patchwork
2019-02-18 15:31 ` [PATCH v2] drm/i915: Restore interrupt enabling after a reset Chris Wilson
2019-02-18 15:38 ` Ville Syrjälä
2019-02-18 16:16 ` ✓ Fi.CI.BAT: success for drm/i915: Restore interrupt enabling after a reset (rev5) Patchwork
2019-02-18 20:21 ` ✓ Fi.CI.IGT: " Patchwork
2019-03-18 13:50 ` [LKP] [drm/i915] a8f0ef1fee: piglit.igt.gem_reset_stats.close-pending-fork-reverse-blt.dmesg-warn kernel test robot
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=20190216001103.7912.76850@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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