public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel@ffwll.ch>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] tests: make color management tests part of the BAT
Date: Tue, 19 Jul 2016 13:21:23 +0100	[thread overview]
Message-ID: <2e044eee-f756-da03-bd04-b275616f40a1@intel.com> (raw)
In-Reply-To: <20160719114236.GG17604@nuc-i3427.alporthouse.com>

On 19/07/16 12:42, Chris Wilson wrote:
> On Tue, Jul 19, 2016 at 08:48:11AM +0200, Daniel Vetter wrote:
>> On Fri, Jul 15, 2016 at 03:00:59PM +0100, Lionel Landwerlin wrote:
>>> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>> Do we have the time for those in the BAT budget?
> Do we not? It has been demonstrated that people notice when gamma is
> broken, can we afford to risk repeating this bug?
>
> (Or in other news, where are all the new QA bugs from failing tests?
> Seems like we are missing some bug reports from igt added to show off
> bugs.)
> -Chris
>
It's about 35s to run this test :
real    0m34.352s
user    0m0.972s
sys    0m1.626s

Knowing that we repeat the same tests across different pipes (so for it 
would only take a third of that time if we were to just test pipe A).

I don't have a sense of the budget, is that too much already?

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

  reply	other threads:[~2016-07-19 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 14:00 [PATCH i-g-t] tests: make color management tests part of the BAT Lionel Landwerlin
2016-07-19  6:48 ` Daniel Vetter
2016-07-19 11:42   ` Chris Wilson
2016-07-19 12:21     ` Lionel Landwerlin [this message]
2016-07-19 12:49       ` Chris Wilson
2016-07-19 13:07         ` Lionel Landwerlin
2016-07-19 14:32     ` Daniel Vetter

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=2e044eee-f756-da03-bd04-b275616f40a1@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --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