From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [1/6] drm/i915: Signal the fences as they are cancelled due to wedging
Date: Thu, 29 Nov 2018 21:36:29 -0000 [thread overview]
Message-ID: <20181129213629.5827.18869@emeril.freedesktop.org> (raw)
In-Reply-To: <20181129205053.27600-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/6] drm/i915: Signal the fences as they are cancelled due to wedging
URL : https://patchwork.freedesktop.org/series/53283/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5226 -> Patchwork_10964
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_10964 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_10964, 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/53283/revisions/1/mbox/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_10964:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live_sanitycheck:
- fi-bxt-dsi: PASS -> DMESG-WARN
* {igt@runner@aborted}:
- fi-bxt-dsi: NOTRUN -> FAIL
Known issues
------------
Here are the changes found in Patchwork_10964 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s4-devices:
- fi-ivb-3520m: PASS -> FAIL [fdo#108880]
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a:
- fi-byt-clapper: PASS -> FAIL [fdo#107362]
* {igt@runner@aborted}:
- {fi-icl-y}: NOTRUN -> FAIL [fdo#108070]
#### Possible fixes ####
* igt@gem_ctx_create@basic-files:
- fi-bsw-n3050: FAIL [fdo#108656] -> PASS
* igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence:
- fi-byt-clapper: FAIL [fdo#103191] / [fdo#107362] -> PASS
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
[fdo#108070]: https://bugs.freedesktop.org/show_bug.cgi?id=108070
[fdo#108656]: https://bugs.freedesktop.org/show_bug.cgi?id=108656
[fdo#108880]: https://bugs.freedesktop.org/show_bug.cgi?id=108880
Participating hosts (49 -> 43)
------------------------------
Additional (1): fi-icl-y
Missing (7): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-pnv-d510
Build changes
-------------
* Linux: CI_DRM_5226 -> Patchwork_10964
CI_DRM_5226: 70ad55640e884b31fb19a0e73fa68cb9c99a69f0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4736: 285ebfb3b7adc56586031afa5150c4e5ad40c229 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10964: 9f108cf790c4eb233666710cc9139d01f02494d8 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
9f108cf790c4 drm/i915: Pipeline PDP updates for Braswell
ea856854af2b drm/i915/selftests: Reorder request allocation vs vma pinning
fe267725e201 drm/i915/selftests: Terminate hangcheck sanitycheck forcibly
87a79e3ccf73 drm/i915: Allocate a common scratch page
0d60aba58d0d drm/i915/ringbuffer: Clear semaphore sync registers on ring init
63398c8a4108 drm/i915: Signal the fences as they are cancelled due to wedging
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10964/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-11-29 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 20:50 [PATCH 1/6] drm/i915: Signal the fences as they are cancelled due to wedging Chris Wilson
2018-11-29 20:50 ` [PATCH 2/6] drm/i915/ringbuffer: Clear semaphore sync registers on ring init Chris Wilson
2018-11-29 20:50 ` [PATCH 3/6] drm/i915: Allocate a common scratch page Chris Wilson
2018-11-29 20:50 ` [PATCH 4/6] drm/i915/selftests: Terminate hangcheck sanitycheck forcibly Chris Wilson
2018-11-29 20:50 ` [PATCH 5/6] drm/i915/selftests: Reorder request allocation vs vma pinning Chris Wilson
2018-11-29 20:50 ` [PATCH 6/6] drm/i915: Pipeline PDP updates for Braswell Chris Wilson
2018-11-29 21:20 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Signal the fences as they are cancelled due to wedging Patchwork
2018-11-29 21:22 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-29 21:36 ` Patchwork [this message]
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=20181129213629.5827.18869@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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