From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() (rev2)
Date: Fri, 29 May 2020 10:44:58 -0000 [thread overview]
Message-ID: <159074909845.3332.2564615585242047787@emeril.freedesktop.org> (raw)
In-Reply-To: <20200529085809.23691-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() (rev2)
URL : https://patchwork.freedesktop.org/series/77781/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8552 -> Patchwork_17813
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17813 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_17813, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17813/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_17813:
### IGT changes ###
#### Possible regressions ####
* igt@runner@aborted:
- fi-bwr-2160: NOTRUN -> [FAIL][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17813/fi-bwr-2160/igt@runner@aborted.html
Known issues
------------
Here are the changes found in Patchwork_17813 that come from known issues:
### IGT changes ###
#### Warnings ####
* igt@i915_pm_rpm@module-reload:
- fi-kbl-x1275: [SKIP][2] ([fdo#109271]) -> [FAIL][3] ([i915#62] / [i915#95])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8552/fi-kbl-x1275/igt@i915_pm_rpm@module-reload.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17813/fi-kbl-x1275/igt@i915_pm_rpm@module-reload.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (50 -> 43)
------------------------------
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8552 -> Patchwork_17813
CI-20190529: 20190529
CI_DRM_8552: cd4a9b47339259e3a98601fff14438f17fd2d7dc @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5683: 757b6e72d546fd2dbc3801a73796d67b0854021b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17813: 39714304d5c296d6f0737d6bf32b9c4a6e901d79 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
39714304d5c2 drm/i915: Check for awaits on still currently executing requests
711dac999c56 drm/i915: Add a few asserts around handling of i915_request_is_active()
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17813/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-29 10:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 8:58 [Intel-gfx] [PATCH 1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() Chris Wilson
2020-05-29 8:58 ` [Intel-gfx] [PATCH 2/2] drm/i915: Once executed, always executed Chris Wilson
2020-05-29 10:09 ` [Intel-gfx] [PATCH v2] drm/i915: Check for awaits on still currently executing requests Chris Wilson
2020-05-29 10:17 ` [Intel-gfx] [PATCH v3] " Chris Wilson
2020-05-29 12:28 ` [Intel-gfx] [PATCH v4] " Chris Wilson
2020-05-29 14:03 ` Chris Wilson
2020-05-29 14:39 ` [Intel-gfx] [PATCH v2] " Chris Wilson
2020-05-29 16:01 ` Tvrtko Ursulin
2020-05-29 9:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() Patchwork
2020-05-29 10:31 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-05-29 10:44 ` Patchwork [this message]
2020-05-29 11:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() (rev3) Patchwork
2020-05-29 12:54 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-05-29 13:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() (rev4) Patchwork
2020-05-29 13:57 ` [Intel-gfx] [PATCH 1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() Tvrtko Ursulin
2020-05-29 14:44 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() (rev4) Patchwork
2020-05-29 15:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() (rev5) Patchwork
2020-05-29 17:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-05-29 17:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Add a few asserts around handling of i915_request_is_active() (rev6) Patchwork
2020-05-29 20:07 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=159074909845.3332.2564615585242047787@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;
as well as URLs for NNTP newsgroup(s).