From: Martin Peres <martin.peres@intel.com>
To: "Summers, Stuart" <stuart.summers@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: ✓ Fi.CI.BAT: success for drm/i915: Allow set context SSEU on platforms after gen 11
Date: Thu, 19 Sep 2019 11:01:00 +0300 [thread overview]
Message-ID: <65e1f878-f53f-8a77-cfb9-53e787584367@intel.com> (raw)
In-Reply-To: <cc47519a241b5eb4fe3d6afa6b790d0c5854e322.camel@intel.com>
On 18/09/2019 23:28, Summers, Stuart wrote:
> On Wed, 2019-09-18 at 19:31 +0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: drm/i915: Allow set context SSEU on platforms after gen 11
>> URL : https://patchwork.freedesktop.org/series/66870/
>> State : success
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_6917 -> Patchwork_14447
>> ====================================================
>>
>> Summary
>> -------
>>
>> **SUCCESS**
>>
>> No regressions found.
>>
>> External URL:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/
>>
>> Known issues
>> ------------
>>
>> Here are the changes found in Patchwork_14447 that come from known
>> issues:
>>
>> ### IGT changes ###
>>
>> #### Issues hit ####
>>
>> * igt@debugfs_test@read_all_entries:
>> - fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724])
>> +1 similar issue
>> [1]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6917/fi-icl-u3/igt@debugfs_test@read_all_entries.html
>> [2]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/fi-icl-u3/igt@debugfs_test@read_all_entries.html
>>
>> * igt@i915_module_load@reload:
>> - fi-icl-u3: [PASS][3] -> [DMESG-WARN][4] ([fdo#107724]
>> / [fdo#111214])
>> [3]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6917/fi-icl-u3/igt@i915_module_load@reload.html
>> [4]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/fi-icl-u3/igt@i915_module_load@reload.html
>>
>> * igt@i915_selftest@live_hangcheck:
>> - fi-icl-u3: [PASS][5] -> [INCOMPLETE][6] ([fdo#107713]
>> / [fdo#108569])
>> [5]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6917/fi-icl-u3/igt@i915_selftest@live_hangcheck.html
>> [6]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/fi-icl-u3/igt@i915_selftest@live_hangcheck.html
>>
>> * igt@kms_chamelium@dp-edid-read:
>> - fi-icl-u2: [PASS][7] -> [FAIL][8] ([fdo#109483] /
>> [fdo#109635 ])
>> [7]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6917/fi-icl-u2/igt@kms_chamelium@dp-edid-read.html
>> [8]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/fi-icl-u2/igt@kms_chamelium@dp-edid-read.html
>>
>> * igt@kms_frontbuffer_tracking@basic:
>> - fi-icl-u2: [PASS][9] -> [FAIL][10] ([fdo#103167])
>> [9]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6917/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
>> [10]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
>>
>>
>> #### Possible fixes ####
>>
>> * igt@gem_ctx_create@basic-files:
>> - {fi-tgl-u}: [INCOMPLETE][11] ([fdo#111735]) ->
>> [PASS][12]
>> [11]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6917/fi-tgl-u/igt@gem_ctx_create@basic-files.html
>> [12]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/fi-tgl-u/igt@gem_ctx_create@basic-files.html
>>
>> * igt@gem_exec_suspend@basic-s3:
>> - fi-blb-e6850: [INCOMPLETE][13] ([fdo#107718]) ->
>> [PASS][14]
>> [13]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6917/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html
>> [14]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html
>>
>> * igt@gem_mmap_gtt@basic-write-no-prefault:
>> - fi-icl-u3: [DMESG-WARN][15] ([fdo#107724]) ->
>> [PASS][16] +1 similar issue
>> [15]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6917/fi-icl-u3/igt@gem_mmap_gtt@basic-write-no-prefault.html
>> [16]:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/fi-icl-u3/igt@gem_mmap_gtt@basic-write-no-prefault.html
>>
>>
>> {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#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
>> [fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
>> [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
>> [fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
>> [fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483
>> [fdo#109635 ]: https://bugs.freedesktop.org/show_bug.cgi?id=109635
>> [fdo#111214]: https://bugs.freedesktop.org/show_bug.cgi?id=111214
>> [fdo#111735]: https://bugs.freedesktop.org/show_bug.cgi?id=111735
>>
>>
>> Participating hosts (53 -> 47)
>> ------------------------------
>>
>> Additional (1): fi-bxt-dsi
>> Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan
>> fi-icl-y fi-byt-clapper fi-bdw-samus
>
> Hi Martin,
>
> Is there an easy way to tell if these missing machines are a result of
> changes made to the patches here vs something else in the test
> infrastructure?
Thanks for asking!
Sometimes, some machines fail to boot for reasons unrelated to the patch
series. We introduced the ci@boot test to be able to tell them apart,
but this is WIP (https://bugs.freedesktop.org/show_bug.cgi?id=111208)...
In the mean time, the best you can do is look at the result grid... Sorry!
Martin
>
> Thanks,
> Stuart
>
>>
>>
>> Build changes
>> -------------
>>
>> * CI: CI-20190529 -> None
>> * Linux: CI_DRM_6917 -> Patchwork_14447
>>
>> CI-20190529: 20190529
>> CI_DRM_6917: 7ca2b123ae999133223b882e3190955897df8b03 @
>> git://anongit.freedesktop.org/gfx-ci/linux
>> IGT_5191: 63e30122cadaf2798ae2bd44a56cee81a27fbc40 @
>> git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>> Patchwork_14447: 807439de93492cd02c3b104effc28780aea605b8 @
>> git://anongit.freedesktop.org/gfx-ci/linux
>>
>>
>> == Linux commits ==
>>
>> 807439de9349 drm/i915: Allow set context SSEU on platforms after gen
>> 11
>>
>> == Logs ==
>>
>> For more details see:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14447/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:[~2019-09-19 8:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 17:31 [PATCH] drm/i915: Allow set context SSEU on platforms after gen 11 Stuart Summers
2019-09-18 19:31 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-09-18 20:28 ` Summers, Stuart
2019-09-19 8:01 ` Martin Peres [this message]
2019-09-18 20:39 ` [PATCH] " Daniele Ceraolo Spurio
2019-09-20 21:10 ` Summers, Stuart
2019-09-19 7:00 ` Tvrtko Ursulin
2019-09-20 21:09 ` Summers, Stuart
2019-09-20 21:29 ` Chris Wilson
2019-09-20 21:36 ` Summers, Stuart
2019-09-23 10:34 ` Tvrtko Ursulin
2019-09-19 8:00 ` ✓ Fi.CI.IGT: success for " 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=65e1f878-f53f-8a77-cfb9-53e787584367@intel.com \
--to=martin.peres@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stuart.summers@intel.com \
/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.