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). Not being able to complete under a 5min makes BAT useless and more than once you mention that even at their current runtime some GEM tests have to have a higher runtime to trigger relevant bugs, which in your own words it makes sense to have them run for (some) extended period of time. Even though running once per night has some disadvantage if the tests are reliable if won't be that hard to catch the regression(s). On Fri, May 27, 2016 at 05:37:15PM +0100, Chris Wilson wrote: > On Fri, May 27, 2016 at 07:27:46PM +0300, Marius Vlad wrote: > > You are lacking an explanation. Please tell me what this test is about > and why it is not suitable criteria for a basic acceptance test. > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
