From: Petri Latvala <petri.latvala@intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: igt-dev@lists.freedesktop.org, Martin Peres <martin.peres@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] tests/intel-ci/blacklist: Blacklist kms_chamelium@hdmi-*-planes-random
Date: Mon, 16 Mar 2020 11:05:51 +0200 [thread overview]
Message-ID: <20200316090551.GC9497@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20200313152911.580802-1-arkadiusz.hiler@intel.com>
On Fri, Mar 13, 2020 at 05:29:10PM +0200, Arkadiusz Hiler wrote:
> Tends to generate invalid configurations using CCS planes or
> configurations that exceed HW capabilities resulting in sporadic failure
> with -EINVAL.
>
> Maintaining extra constraints for Intel's HW is too costly in comparison
> to the value provided.
>
> Seems like the test is used by other vendors, so unless they are fine
> with removal we'll keep it. In the meantime let's blacklist it for our
> CI.
>
> Fixes: https://gitlab.freedesktop.org/drm/intel/issues/1404
> Fixes: https://gitlab.freedesktop.org/drm/intel/issues/239
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Martin Peres <martin.peres@intel.com>
> Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
> ---
> tests/intel-ci/blacklist.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
> index 8085719f..a7bd1e68 100644
> --- a/tests/intel-ci/blacklist.txt
> +++ b/tests/intel-ci/blacklist.txt
> @@ -69,6 +69,17 @@ igt@gen7_exec_parse@.*lri.*
> ###############################################
> igt@kms_frontbuffer_tracking@.*drrs.*
> ###############################################
> +# Tends to generate invalid configurations
> +# using CCS planes or configurations that
> +# exceed HW capabilities resulting in sporadic
> +# failure with -EINVAL.
> +#
> +# Maintaining extra constraints for Intel's HW
> +# is too costly in comparison to the value
> +# provided.
> +###############################################
> +igt@kms_chamelium@hdmi-.*-planes-random
> +###############################################
> # Broadcom
> ###############################################
> igt@vc4_.*
> --
> 2.24.1
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-03-16 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 15:29 [igt-dev] [PATCH i-g-t 1/2] tests/intel-ci/blacklist: Blacklist kms_chamelium@hdmi-*-planes-random Arkadiusz Hiler
2020-03-13 15:29 ` [igt-dev] [PATCH i-g-t 2/2] tests/kms_chamelium: Get rid of dp-link-status subtest Arkadiusz Hiler
2020-03-16 9:07 ` Petri Latvala
2020-03-16 10:06 ` Arkadiusz Hiler
2020-03-13 16:16 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/2] tests/intel-ci/blacklist: Blacklist kms_chamelium@hdmi-*-planes-random Patchwork
2020-03-16 10:10 ` Arkadiusz Hiler
2020-03-16 10:57 ` Vudum, Lakshminarayana
2020-03-16 9:05 ` Petri Latvala [this message]
2020-03-16 10:52 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-03-16 13:43 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20200316090551.GC9497@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=martin.peres@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