From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/selftests: Workaround an issue with unused lockdep subclass (rev2)
Date: Thu, 15 Nov 2018 21:31:10 -0000 [thread overview]
Message-ID: <20181115213110.11615.95822@emeril.freedesktop.org> (raw)
In-Reply-To: <20181115174511.8358-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/selftests: Workaround an issue with unused lockdep subclass (rev2)
URL : https://patchwork.freedesktop.org/series/52551/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5147 -> Patchwork_10833 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/52551/revisions/2/mbox/
== Known issues ==
Here are the changes found in Patchwork_10833 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@drv_selftest@live_hangcheck:
fi-bwr-2160: PASS -> DMESG-FAIL (fdo#108735)
igt@kms_flip@basic-plain-flip:
fi-ilk-650: PASS -> DMESG-WARN (fdo#106387)
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
fi-byt-clapper: PASS -> FAIL (fdo#103191, fdo#107362)
==== Possible fixes ====
igt@gem_exec_suspend@basic-s3:
fi-icl-u2: DMESG-WARN (fdo#107724) -> PASS
igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence:
fi-byt-clapper: FAIL (fdo#103191, fdo#107362) -> PASS +2
igt@pm_rpm@module-reload:
fi-skl-6770hq: DMESG-WARN (fdo#105541) -> PASS
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#105541 https://bugs.freedesktop.org/show_bug.cgi?id=105541
fdo#106387 https://bugs.freedesktop.org/show_bug.cgi?id=106387
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107724 https://bugs.freedesktop.org/show_bug.cgi?id=107724
fdo#108735 https://bugs.freedesktop.org/show_bug.cgi?id=108735
== Participating hosts (51 -> 43) ==
Missing (8): fi-ilk-m540 fi-icl-u fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-snb-2520m fi-ctg-p8600 fi-kbl-7560u
== Build changes ==
* Linux: CI_DRM_5147 -> Patchwork_10833
CI_DRM_5147: 7d2b7a6073309f870689b91fa4c4a30120ccbe00 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4715: 111593c49d812a4f4ff9ab0ef053a3ab88a6f73f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10833: 4a050d13fb0fd034e8f8c07aa82c7da14a81ecbc @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
4a050d13fb0f drm/i915/selftests: Workaround an issue with unused lockdep subclass
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10833/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-11-15 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 17:45 [PATCH] drm/i915/selftests: Workaround an issue with unused lockdep subclass Chris Wilson
2018-11-15 18:12 ` Matthew Auld
2018-11-15 18:38 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-11-15 20:38 ` [PATCH] " Chris Wilson
2018-11-15 21:31 ` Patchwork [this message]
2018-11-15 23:56 ` ✓ Fi.CI.IGT: success for drm/i915/selftests: Workaround an issue with unused lockdep subclass (rev2) 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=20181115213110.11615.95822@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