Re: [Intel-gfx] [PATCH igt 1/2] intel-ci: Do module reload last

2017-01-18 Thread Petri Latvala
On Wed, Jan 18, 2017 at 10:21:47AM +, Chris Wilson wrote: > On Wed, Jan 18, 2017 at 12:14:00PM +0200, Petri Latvala wrote: > > Thanks for the reminder about this ordering change. > > > > The crash from disable_display use will cause $stuff in CI, its > > ability to recover and resume is not

Re: [Intel-gfx] [PATCH igt 1/2] intel-ci: Do module reload last

2017-01-18 Thread Chris Wilson
On Wed, Jan 18, 2017 at 12:14:00PM +0200, Petri Latvala wrote: > Thanks for the reminder about this ordering change. > > The crash from disable_display use will cause $stuff in CI, its > ability to recover and resume is not quite there yet. But as it's at > the end, we can live with it until a

Re: [Intel-gfx] [PATCH igt 1/2] intel-ci: Do module reload last

2017-01-18 Thread Petri Latvala
Thanks for the reminder about this ordering change. The crash from disable_display use will cause $stuff in CI, its ability to recover and resume is not quite there yet. But as it's at the end, we can live with it until a fix lands. Series is Acked-by: Petri Latvala

[Intel-gfx] [PATCH igt 1/2] intel-ci: Do module reload last

2017-01-18 Thread Chris Wilson
We want to run the initial set of tests under "pristine startup" conditions - so that our tests see the hardware as close to the condition we normally would after booting. This means that we want to avoid reloading the module until the very last set of tests. Signed-off-by: Chris Wilson