[Intel-gfx] [PATCH i-g-t v2] scripts: add quick-testlist.py

Feceoru, Gabriel gabriel.feceoru at intel.com
Thu Sep 17 07:01:14 PDT 2015

This script measures the duration of the subtests. But in case of gem_concurrent_all, 
for instance, there are 3780 subtests for which, although many shorter than 60s, the total
duration will not qualify this for a quick test (~2h).

Thank you,
From: Intel-gfx [intel-gfx-bounces at lists.freedesktop.org] on behalf of Chris Wilson [chris at chris-wilson.co.uk]
Sent: Thursday, September 17, 2015 3:43 PM
To: Wood, Thomas
Cc: Intel Graphics Development
Subject: Re: [Intel-gfx] [PATCH i-g-t v2] scripts: add quick-testlist.py

On Thu, Sep 17, 2015 at 01:16:18PM +0100, Thomas Wood wrote:
> On 17 September 2015 at 13:09, Chris Wilson <chris at chris-wilson.co.uk> wrote:
> > On Thu, Sep 17, 2015 at 12:42:44PM +0100, Thomas Wood wrote:
> >> Add a script to take a piglit results file and create a list of tests
> >> that ran in under 60 seconds. This list can be used by the --test-list
> >> option of piglit.
> >
> > And passed?
> Any status except "incomplete", which normally means a reboot was
> required. It might also be worth noting that tests skipped on one
> platform may not skip on another, so the output only really applies to
> the platform the results were initially produced on.

My point is that the timing can only be expected to be consistent for a
pass. A failure may be quick, but success may take a few hours.

Chris Wilson, Intel Open Source Technology Centre
Intel-gfx mailing list
Intel-gfx at lists.freedesktop.org

More information about the Intel-gfx mailing list