public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tomi Sarvela <tomi.p.sarvela@intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	intel-gfx@lists.freedesktop.org, "Lofstedt,
	Marta" <marta.lofstedt@intel.com>,
	"Peres, Martin" <martin.peres@intel.com>
Subject: Re: [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)
Date: Wed, 08 Nov 2017 17:59:30 +0200	[thread overview]
Message-ID: <87zi7wahi5.fsf@intel.com> (raw)
In-Reply-To: <6d0de55c-e67a-c4eb-5a76-83f4448e13f2@intel.com>

On Wed, 08 Nov 2017, Tomi Sarvela <tomi.p.sarvela@intel.com> wrote:
> On 08/11/17 17:27, Jani Nikula wrote:
>> On Wed, 08 Nov 2017, Chris Wilson <chris@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@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.

BR,
Jani.


>
> Tomi

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-08 15:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 11:11 [PATCH] HAX: WARN_ON(crtc->crc.opened during disable) Maarten Lankhorst
2017-11-08 11:20 ` Ville Syrjälä
2017-11-08 13:06 ` Jani Nikula
2017-11-08 14:59   ` Chris Wilson
2017-11-08 15:27     ` Jani Nikula
2017-11-08 15:38       ` Tomi Sarvela
2017-11-08 15:59         ` Jani Nikula [this message]
2017-11-08 16:15           ` Martin Peres
2017-11-09  9:09             ` Jani Nikula
2017-11-09  8:39           ` Tomi Sarvela
2017-11-08 14:39 ` ✗ Fi.CI.BAT: warning for " Patchwork

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=87zi7wahi5.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marta.lofstedt@intel.com \
    --cc=martin.peres@intel.com \
    --cc=tomi.p.sarvela@intel.com \
    /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