intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Ben Widawsky <ben-Egm8mFWDmf3k1uMJSBkQmQ@public.gmane.org>
To: Daniel Vetter <daniel.vetter-/w4YWyX8dFk@public.gmane.org>
Cc: piglit discussion list
	<piglit-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	Intel Graphics Development
	<intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH] tests/igt: Add runtime environment checks
Date: Tue, 26 Nov 2013 12:02:39 -0800	[thread overview]
Message-ID: <20131126200238.GE27358@bwidawsk.net> (raw)
In-Reply-To: <CAKMK7uEeyNShA8fAF82+prCgYTVd2G60GLVMCCVy56p2uRGeJA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tue, Nov 26, 2013 at 08:55:40PM +0100, Daniel Vetter wrote:
> On Tue, Nov 26, 2013 at 8:53 PM, Damien Lespiau
> <damien.lespiau-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> > On Tue, Nov 26, 2013 at 11:49:43AM -0800, Ben Widawsky wrote:
> >> > Only in the make target he created, not in piglit itself. Imo we should
> >> > have all the testrunner logic in one place, i.e. in the piglit sources.
> >> > -Daniel
> >>
> >> Damien, can you comment? I could have sworn you said something different
> >> on IRC. It sounded like exactly what I wanted.
> >
> > What Daniel says is correct, the check is part of the runner wrapper,
> > not piglit itself.
> >
> > I'd rather have a environement check up-front and I don't mind where it
> > lives (igt Vs piglit).
> 
> The problem is that generating the testlist (or printing the commands)
> is a feature QA actually relies on. I also use it occasionally to
> quickly test igt library changes. So we can't bail that early. My
> patch bails fairly late, but I didn't see a better spot.
> -Daniel

I'm confused then about how this really improves my current situation.

-- 
Ben Widawsky, Intel Open Source Technology Center

  parent reply	other threads:[~2013-11-26 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26  8:09 [PATCH] tests/igt: Add runtime environment checks Daniel Vetter
2013-11-26 19:05 ` Ben Widawsky
     [not found]   ` <20131126190556.GB27358-Egm8mFWDmf3k1uMJSBkQmQ@public.gmane.org>
2013-11-26 19:46     ` Daniel Vetter
     [not found]       ` <20131126194619.GS27344-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2013-11-26 19:49         ` Ben Widawsky
2013-11-26 19:53           ` Damien Lespiau
     [not found]             ` <20131126195332.GC32421-q+Y1yDQJ1rKUyhp/hE4EWxL4W9x8LtSr@public.gmane.org>
2013-11-26 19:55               ` Daniel Vetter
     [not found]                 ` <CAKMK7uEeyNShA8fAF82+prCgYTVd2G60GLVMCCVy56p2uRGeJA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-26 20:02                   ` Ben Widawsky [this message]
     [not found]                     ` <20131126200238.GE27358-Egm8mFWDmf3k1uMJSBkQmQ@public.gmane.org>
2013-11-26 21:51                       ` Daniel Vetter
     [not found] ` <1385453344-25217-1-git-send-email-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2013-11-26 21:15   ` 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=20131126200238.GE27358@bwidawsk.net \
    --to=ben-egm8mfwdmf3k1umjsbkqmq@public.gmane.org \
    --cc=daniel.vetter-/w4YWyX8dFk@public.gmane.org \
    --cc=intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=piglit-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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;
as well as URLs for NNTP newsgroup(s).