[Intel-gfx] [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)

[Tomi Sarvela]

On 08/11/17 17:59, Jani Nikula wrote:
> On Wed, 08 Nov 2017, Tomi Sarvela <tomi.p.sarvela at intel.com> wrote:
>> On 08/11/17 17:27, Jani Nikula wrote:
>>> On Wed, 08 Nov 2017, Chris Wilson <chris at chris-wilson.co.uk> wrote:
>>>> Quoting Jani Nikula (2017-11-08 13:06:39)
>>>>>
>>>>> Please use trybot (i.e. send patches to
>>>>> intel-gfx-trybot at lists.freedesktop.org) for hacks that aren't intended
>>>>> for upstream. Then they can be prioritized appropriately.
>>>>
>>>> We don't have excess to the extended test run on trybot yet...
>>>
>>> Marta, Martin, Tomi - this.
>>>
>>> Though I believe Chris wants access not excess. ;)
>>
>> Sssooo... shard-runs for Trybot? Only on success, or also on warning as
>> with intel-gfx and igt?
>>
>> The very recent change to run also f-feedback warnings on shards, and
>> fixed vetting handling, will cause much more shardruns.
>>
>> After KBL DMC update it could be taken to all the runs, instead of
>> avoiding it because it's 20 minutes slower (and GLK is 30 minutes more
>> slower)
>>
>> We'll see if there's enough time in a day.
> 
> IIUC there currently just isn't. The problem is, people are now running
> their hack patches on the regular CI to get full runs, and we can't even
> prioritize the stuff aimed at upstream over hacks.

If there is possibility to prioritize lower by sending hacks to Trybot, 
it might be enough. I don't mind queue if more important stuff is tested 
timely and trybot comes later.

Tomi
-- 
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo