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 drm/i915: Skip object locking around a no-op set-domain ioctl
Date: Thu, 21 Mar 2019 09:04:59 -0000 [thread overview]
Message-ID: <20190321090459.14934.30165@emeril.freedesktop.org> (raw)
In-Reply-To: <20190321080532.18381-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Skip object locking around a no-op set-domain ioctl
URL : https://patchwork.freedesktop.org/series/58325/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5785 -> Patchwork_12542
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_12542 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_12542, 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/58325/revisions/1/mbox/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_12542:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_reloc@basic-cpu-active:
- fi-bsw-kefka: PASS -> FAIL +7
- fi-hsw-4770r: PASS -> FAIL +3
- fi-cfl-8109u: PASS -> FAIL +3
- fi-byt-clapper: PASS -> FAIL +7
- fi-ivb-3770: PASS -> FAIL +3
- fi-icl-u3: PASS -> FAIL +3
- fi-skl-gvtdvm: PASS -> FAIL +2
* igt@gem_exec_reloc@basic-gtt-active:
- fi-snb-2520m: PASS -> CRASH +1
* igt@gem_exec_reloc@basic-gtt-cpu:
- fi-byt-n2820: PASS -> FAIL +6
- fi-elk-e7500: PASS -> FAIL +9
- fi-ilk-650: PASS -> FAIL +8
* igt@gem_exec_reloc@basic-gtt-cpu-active:
- fi-kbl-8809g: PASS -> FAIL +3
- fi-kbl-x1275: PASS -> FAIL +3
- fi-skl-6600u: PASS -> FAIL +3
- fi-pnv-d510: PASS -> FAIL +6
- fi-apl-guc: PASS -> FAIL +3
- fi-skl-6700k2: PASS -> FAIL +3
- fi-bxt-j4205: PASS -> FAIL +3
* igt@gem_exec_reloc@basic-gtt-cpu-noreloc:
- fi-bwr-2160: PASS -> FAIL +7
- fi-gdg-551: PASS -> FAIL +4
* igt@gem_exec_reloc@basic-write-cpu-active:
- fi-hsw-4770: PASS -> FAIL +3
- fi-snb-2520m: PASS -> FAIL +4
- fi-skl-guc: PASS -> FAIL +3
- fi-kbl-7500u: PASS -> FAIL +2
- fi-bdw-5557u: PASS -> FAIL +3
- fi-bdw-gvtdvm: PASS -> FAIL +2
- fi-kbl-guc: PASS -> FAIL +3
- fi-whl-u: PASS -> FAIL +3
- fi-kbl-7567u: PASS -> FAIL +3
* igt@gem_exec_reloc@basic-write-cpu-noreloc:
- fi-blb-e6850: PASS -> FAIL +7
- fi-bsw-n3050: PASS -> FAIL +6
- fi-byt-j1900: PASS -> FAIL +7
* igt@gem_exec_reloc@basic-write-gtt-active:
- fi-pnv-d510: PASS -> CRASH +2
- fi-ilk-650: PASS -> CRASH +1
* igt@prime_vgem@basic-fence-mmap:
- fi-cfl-8700k: PASS -> FAIL +3
- fi-skl-iommu: PASS -> FAIL +3
- fi-cfl-guc: PASS -> FAIL +3
- fi-skl-6770hq: PASS -> FAIL +3
- fi-skl-6260u: PASS -> FAIL +3
- fi-kbl-r: PASS -> FAIL +3
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@prime_vgem@basic-fence-mmap:
- {fi-skl-lmem}: PASS -> FAIL +3
Known issues
------------
Here are the changes found in Patchwork_12542 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_evict:
- fi-bsw-kefka: PASS -> DMESG-WARN [fdo#107709]
* igt@kms_frontbuffer_tracking@basic:
- fi-byt-clapper: PASS -> FAIL [fdo#103167]
* igt@kms_pipe_crc_basic@read-crc-pipe-b:
- fi-byt-clapper: PASS -> FAIL [fdo#107362]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
- fi-byt-clapper: PASS -> FAIL [fdo#103191] / [fdo#107362] +3
* igt@runner@aborted:
- fi-bsw-kefka: NOTRUN -> FAIL [fdo#107709]
- fi-apl-guc: NOTRUN -> FAIL [fdo#108622] / [fdo#109720]
#### Possible fixes ####
* igt@kms_busy@basic-flip-b:
- fi-gdg-551: FAIL [fdo#103182] -> PASS
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:
- fi-byt-clapper: FAIL [fdo#103191] / [fdo#107362] -> PASS
* igt@prime_vgem@basic-fence-flip:
- fi-ilk-650: 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#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103182]: https://bugs.freedesktop.org/show_bug.cgi?id=103182
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#104008]: https://bugs.freedesktop.org/show_bug.cgi?id=104008
[fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
[fdo#107709]: https://bugs.freedesktop.org/show_bug.cgi?id=107709
[fdo#108622]: https://bugs.freedesktop.org/show_bug.cgi?id=108622
[fdo#109720]: https://bugs.freedesktop.org/show_bug.cgi?id=109720
Participating hosts (47 -> 39)
------------------------------
Missing (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-hsw-peppy fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_5785 -> Patchwork_12542
CI_DRM_5785: 1e3d80c25878b7d97ad6c0680a452d55baeb28e0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4894: fedd92f4022837e2c20e472b65bd7d0849f484a3 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12542: e968397bb2a0f670008379e48b8e228dd0780bbd @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
e968397bb2a0 drm/i915: Skip object locking around a no-op set-domain ioctl
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12542/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-21 9:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 8:05 [PATCH] drm/i915: Skip object locking around a no-op set-domain ioctl Chris Wilson
2019-03-21 8:41 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-03-21 9:04 ` Patchwork [this message]
2019-03-21 9:11 ` ✗ Fi.CI.BAT: failure " Chris Wilson
2019-03-21 9:21 ` Chris Wilson
2019-03-21 9:14 ` [PATCH] " Chris Wilson
2019-03-21 9:17 ` Chris Wilson
2019-03-21 9:35 ` [PATCH v3] " Chris Wilson
2019-03-21 9:44 ` [PATCH v4] " Chris Wilson
2019-03-21 12:36 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Skip object locking around a no-op set-domain ioctl (rev4) Patchwork
2019-03-21 12:59 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-22 1:31 ` ✓ 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=20190321090459.14934.30165@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.