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 HAX: poison the CSB after use (rev3)
Date: Mon, 29 Oct 2018 15:19:59 -0000 [thread overview]
Message-ID: <20181029151959.26193.79934@emeril.freedesktop.org> (raw)
In-Reply-To: <20181029134313.21608-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: HAX: poison the CSB after use (rev3)
URL : https://patchwork.freedesktop.org/series/51677/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5045 -> Patchwork_10626 =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_10626 need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_10626, 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/51677/revisions/3/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_10626:
=== IGT changes ===
==== Warnings ====
igt@drv_selftest@live_guc:
fi-icl-u: SKIP -> PASS +2
== Known issues ==
Here are the changes found in Patchwork_10626 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@kms_flip@basic-flip-vs-dpms:
fi-hsw-4770r: PASS -> DMESG-WARN (fdo#105602)
igt@kms_pipe_crc_basic@hang-read-crc-pipe-b:
fi-byt-clapper: PASS -> FAIL (fdo#103191, fdo#107362)
igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a:
fi-icl-u2: PASS -> DMESG-WARN (fdo#106107)
igt@kms_pipe_crc_basic@read-crc-pipe-a:
fi-byt-clapper: PASS -> FAIL (fdo#107362)
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
fi-byt-clapper: PASS -> INCOMPLETE (fdo#102657)
==== Possible fixes ====
igt@drv_selftest@live_contexts:
fi-icl-u: INCOMPLETE (fdo#108535) -> PASS
igt@drv_selftest@live_hangcheck:
fi-skl-guc: DMESG-FAIL -> PASS
igt@kms_flip@basic-flip-vs-dpms:
fi-skl-6700hq: DMESG-WARN (fdo#105998) -> PASS
fdo#102657 https://bugs.freedesktop.org/show_bug.cgi?id=102657
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#105602 https://bugs.freedesktop.org/show_bug.cgi?id=105602
fdo#105998 https://bugs.freedesktop.org/show_bug.cgi?id=105998
fdo#106107 https://bugs.freedesktop.org/show_bug.cgi?id=106107
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#108535 https://bugs.freedesktop.org/show_bug.cgi?id=108535
== Participating hosts (46 -> 43) ==
Missing (3): fi-ilk-m540 fi-byt-squawks fi-bsw-cyan
== Build changes ==
* Linux: CI_DRM_5045 -> Patchwork_10626
CI_DRM_5045: b5ec1a938aea1befeb92e6a51313f4d637265fdf @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4699: 1270ec553741ac20c45178d2b26f9a9562ea565f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10626: 7c3d3866369dcdc38ac9ae386ec9d42d5cffa9d4 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
7c3d3866369d HAX: poison the CSB after use
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10626/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-10-29 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 13:43 [PATCH] HAX: poison the CSB after use Chris Wilson
2018-10-29 13:49 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-10-29 13:57 ` [PATCH] " Chris Wilson
2018-10-29 14:31 ` ✗ Fi.CI.BAT: failure for HAX: poison the CSB after use (rev2) Patchwork
2018-10-29 14:37 ` [PATCH] HAX: poison the CSB after use Chris Wilson
2018-10-29 14:58 ` ✗ Fi.CI.CHECKPATCH: warning for HAX: poison the CSB after use (rev3) Patchwork
2018-10-29 15:19 ` Patchwork [this message]
2018-10-29 17:19 ` ✓ Fi.CI.IGT: success " 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=20181029151959.26193.79934@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