Quoting Petri Latvala (2018-08-10 10:55:06) > On Fri, Aug 10, 2018 at 10:41:45AM +0100, Chris Wilson wrote: > > Reloading the module may impact subsequent tests by destabilising the > > system. As we do for BAT, if we want to test reloads, it should be > > handled explicitly at the end of the run, rather than placed at random > > in the middle of the test list. > > > > v2: Commentary > > > > References: https://bugs.freedesktop.org/show_bug.cgi?id=106539 > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > Cc: Tomi Sarvela <tomi.p.sarvela@xxxxxxxxx> > > > The series is > > Acked-by: Petri Latvala <petri.latvala@xxxxxxxxx> I've pushed this to see if this does indeed stabilise our test results as currently we have random failures that change on every shardlist rebuild. I think we need an explicit test list to check after reload. I think BAT? -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
