On Fri, Jun 23, 2017 at 12:21:48PM +0100, Chris Wilson wrote:
> Quoting Daniel Vetter (2017-06-23 12:14:49)
> > On Thu, Jun 22, 2017 at 12:45 PM, Tvrtko Ursulin
> > wrote:
> > >
> > > On 22/06/2017 10:54, Daniel Vetter wrote:
> > >>
> > >> On Fri, Jun 16, 2017 at
Quoting Daniel Vetter (2017-06-23 12:14:49)
> On Thu, Jun 22, 2017 at 12:45 PM, Tvrtko Ursulin
> wrote:
> >
> > On 22/06/2017 10:54, Daniel Vetter wrote:
> >>
> >> On Fri, Jun 16, 2017 at 12:55 PM, Tvrtko Ursulin
> >> wrote:
> >>>
> >>> From:
On Thu, Jun 22, 2017 at 12:45 PM, Tvrtko Ursulin
wrote:
>
> On 22/06/2017 10:54, Daniel Vetter wrote:
>>
>> On Fri, Jun 16, 2017 at 12:55 PM, Tvrtko Ursulin
>> wrote:
>>>
>>> From: Tvrtko Ursulin
>>>
>>> Where there
On 22/06/2017 10:54, Daniel Vetter wrote:
On Fri, Jun 16, 2017 at 12:55 PM, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Where there is both default and render for the same test,
remove the former to save some execution time.
If they are
On Fri, Jun 16, 2017 at 12:55 PM, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Where there is both default and render for the same test,
> remove the former to save some execution time.
If they are redundant, why do we even have them? Can we
Quoting Tvrtko Ursulin (2017-06-16 11:55:29)
> From: Tvrtko Ursulin
>
> Where there is both default and render for the same test,
> remove the former to save some execution time.
Fwiw, ack to using a subset of engines in each test. Though I'd prefer
it if we engineered
From: Tvrtko Ursulin
Where there is both default and render for the same test,
remove the former to save some execution time.
Signed-off-by: Tvrtko Ursulin
---
tests/intel-ci/extended.testlist | 21 -
1 file changed, 21