public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.IGT: failure for Add Colorspace connector property interface (rev16)
Date: Wed, 20 Feb 2019 09:57:19 +0100	[thread overview]
Message-ID: <3b04c3d4-530d-a33b-8144-e6f831888516@linux.intel.com> (raw)
In-Reply-To: <E7C9878FBA1C6D42A1CA3F62AEB6945F81F38841@BGSMSX104.gar.corp.intel.com>

Op 20-02-2019 om 07:01 schreef Shankar, Uma:
>
>> -----Original Message-----
>> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf Of
>> Patchwork
>> Sent: Wednesday, February 20, 2019 2:43 AM
>> To: intel-gfx@lists.freedesktop.org
>> Subject: [Intel-gfx] ✗ Fi.CI.IGT: failure for Add Colorspace connector property
>> interface (rev16)
>>
>> == Series Details ==
>>
>> Series: Add Colorspace connector property interface (rev16)
>> URL   : https://patchwork.freedesktop.org/series/47132/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_5632_full -> Patchwork_12260_full
>> ====================================================
>>
>> Summary
>> -------
>>
>>  **FAILURE**
>>
>>  Serious unknown changes coming with Patchwork_12260_full absolutely need to be
>>  verified manually.
>>
>>  If you think the reported changes have nothing to do with the changes
>>  introduced in Patchwork_12260_full, please notify your bug team to allow them
>>  to document this new failure mode, which will reduce false positives in CI.
>>
>>
>>
>> Possible new issues
>> -------------------
>>
>>  Here are the unknown changes that may have been introduced in
>> Patchwork_12260_full:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>>  * igt@pm_rpm@cursor:
>>    - shard-iclb:         PASS -> INCOMPLETE
> This is not related to this change, it seems a false positive. Earlier revision with same change
> had clean IGT pass. This version didn't introduced any major change hence this should be ignored
> and investigated as to why this is coming in the CI runs. Is this already known ?
>
> Regards,
> Uma Shankar


Noticed pm_rpm@cursor failing, but yeah..

Pushed the series, thanks for your patience. :)

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-02-20  8:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 17:12 [v17 0/3] Add Colorspace connector property interface Uma Shankar
2019-02-19 17:12 ` [v17 1/3] drm: Add HDMI colorspace property Uma Shankar
2019-02-19 17:13 ` [v17 2/3] drm: Add colorspace info to AVI Infoframe Uma Shankar
2019-02-19 17:13 ` [v17 3/3] drm/i915: Attach colorspace property and enable modeset Uma Shankar
2019-02-19 17:39 ` ✓ Fi.CI.BAT: success for Add Colorspace connector property interface (rev16) Patchwork
2019-02-19 21:12 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-02-20  6:01   ` Shankar, Uma
2019-02-20  8:57     ` Maarten Lankhorst [this message]
2019-02-20  9:27       ` Shankar, Uma

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=3b04c3d4-530d-a33b-8144-e6f831888516@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=uma.shankar@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