On Mon, May 30, 2016 at 01:44:52PM +0300, Marius Vlad wrote: > The explanation is the same as in the previous series: the GEM tests are > taking too long. Either I sack them under nightly runs or decrease the > runtime. As new tests are added, it will take too long to provide > meaningful output from BAT. There are platforms that reach the timeout > (of 15minutes), and the slowest platform is the one that provides the > runtime for the entire CI system (as we wait and collect the results > from all of them). I am all for improving BAT, dropping tests is not acceptable imo. Replacing them with equivalent-or-better that run quickly should be the goal. Otherwise, you get into the same situation with the nightly runs (that already exclude gem_concurrent_blit despite it being one of the few tools that catch basic errors in GEM). -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
