From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: igt-dev@lists.freedesktop.org,
Martin Peres <martin.peres@linux.intel.com>,
Lakshminarayana Vudum <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] ✓ Fi.CI.IGT: success for DC states igt tests patch series (rev21)
Date: Fri, 20 Sep 2019 15:43:44 +0530 [thread overview]
Message-ID: <d83101c8-09f1-a92e-6a81-6f1a0cba9b4f@intel.com> (raw)
In-Reply-To: <20190920100427.GY4019@platvala-desk.ger.corp.intel.com>
On 9/20/2019 3:34 PM, Petri Latvala wrote:
> On Fri, Sep 20, 2019 at 05:46:32AM +0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: DC states igt tests patch series (rev21)
>> URL : https://patchwork.freedesktop.org/series/56713/
>> State : success
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_6923_full -> IGTPW_3480_full
>> ====================================================
>>
>> Summary
>> -------
>>
>> **SUCCESS**
>>
>> No regressions found.
>>
>> External URL: https://patchwork.freedesktop.org/api/1.0/series/56713/revisions/21/mbox/
>>
>> Possible new issues
>> -------------------
>>
>> Here are the unknown changes that may have been introduced in IGTPW_3480_full:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>> * {igt@i915_pm_dc@dc6-dpms} (NEW):
>> - shard-iclb: NOTRUN -> [FAIL][1]
>> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3480/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html
>> - shard-kbl: NOTRUN -> [FAIL][2]
>> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3480/shard-kbl1/igt@i915_pm_dc@dc6-dpms.html
>
>
> The series looks otherwise good to go, but these two fails need an ack
> from Martin/Lakshmi first for filing bugs and cibuglog filters for
> them.
Hi Petri ,
These failures due to the reason few platform are not able to go to PC8
state.
There is already a bug raised for these failures,
https://bugs.freedesktop.org/show_bug.cgi?id=110548
I have put my analysis there (PCIe express devices blocking it).
Thanks ,
Anshuman Gupta.
>
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-09-20 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 17:30 [igt-dev] [PATCH i-g-t v14 0/6] DC states igt tests patch series Anshuman Gupta
2019-09-19 17:30 ` [igt-dev] [PATCH i-g-t v14 1/6] lib/igt_pm: igt lib helper routines to support DC5/6 tests Anshuman Gupta
2019-09-19 17:30 ` [igt-dev] [PATCH i-g-t v14 3/6] tests/i915/i915_pm_dc: Added test for DC6 during PSR Anshuman Gupta
2019-09-19 17:30 ` [igt-dev] [PATCH i-g-t v14 4/6] tests/i915/i915_pm_dc: Added test for DC5 during DPMS Anshuman Gupta
2019-09-19 17:30 ` [igt-dev] [PATCH i-g-t v14 5/6] tests/i915/i915_pm_dc: Added test for DC6 " Anshuman Gupta
2019-09-19 17:30 ` [igt-dev] [PATCH i-g-t v14 6/6] tests/i915/i915_pm_dc:Skip the DC6 test if BIOS has disabled PC8+ Anshuman Gupta
2019-09-19 18:53 ` [igt-dev] ✓ Fi.CI.BAT: success for DC states igt tests patch series (rev21) Patchwork
2019-09-20 5:46 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-09-20 10:04 ` Petri Latvala
2019-09-20 10:13 ` Gupta, Anshuman [this message]
2019-09-20 10:44 ` Lakshmi
2019-09-20 10:53 ` Petri Latvala
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=d83101c8-09f1-a92e-6a81-6f1a0cba9b4f@intel.com \
--to=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lakshminarayana.vudum@intel.com \
--cc=martin.peres@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox