On Thu, Oct 13, 2016 at 03:00:43PM +0100, Chris Wilson wrote: > Add the two basic gem_wait tests to the fast list, together they take a > total of 1s (when correctly functioning). > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > --- > tests/intel-ci/fast-feedback.testlist | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist > index f59ec98..853b911 100644 > --- a/tests/intel-ci/fast-feedback.testlist > +++ b/tests/intel-ci/fast-feedback.testlist > @@ -126,6 +126,8 @@ igt@gem_sync@basic-store-each > igt@gem_tiled_blits@basic > igt@gem_tiled_fence_blits@basic > igt@gem_tiled_pread_basic > +igt@gem_wait@basic-busy-all > +igt@gem_wait@basic-wait-all > igt@gem_workarounds@basic-read > igt@gvt_basic@invalid-placeholder-test > igt@kms_addfb_basic@addfb25-bad-modifier > -- > 2.9.3 In the future we will test new tests in the CI system. Unfortunately the technology isn't there yet (tm) so this had to be tested manually. Sorry for the delay. For the record, the testing requirements for incoming new tests is converging to: - Tests must be stable. 1000 repeated runs with the new tests alone must give the same results. 10 repeated runs of modified BAT set must give the same results (excluding known issues in other tests). - Tests must be fast. Full modified BAT run must not exceed the time budget. - Tests must pass on current kernels, on some platform. This will be documented when we can get CI do the testing for us on multiple platforms and properly know what kind of requirements can actually be tested. For these tests, manual testing was done on IVB, HSW, and BYT. Stable, fast and passing on all. Acked-by: Petri Latvala <petri.latvala@xxxxxxxxx> Please push. -- Petri Latvala _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
