[Intel-gfx] [PATCH i-g-t 6/7] tests/kms_flip: Increase TEST_TS_CONT max seq difference to 150

Daniel Vetter daniel at ffwll.ch
Wed Dec 16 02:49:11 PST 2015


On Mon, Dec 14, 2015 at 10:15:55PM +0200, ville.syrjala at linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala at linux.intel.com>
> 
> During suspend tests we can exceed the current 100 frame difference
> in sequence numbers. Bump the limit to 150 frames.
> 
> Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>

I'd bump a lot more tbh, or maybe check for system suspend/resume and then
bump to 1000, otherwise leave at 100.
-Daniel

> ---
>  tests/kms_flip.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/kms_flip.c b/tests/kms_flip.c
> index 750a1882dc3c..0dae83046b20 100644
> --- a/tests/kms_flip.c
> +++ b/tests/kms_flip.c
> @@ -674,9 +674,9 @@ static void check_state(struct test_output *o, struct event_state *es)
>  		igt_assert_f(es->current_seq - es->last_seq >= 0,
>  			     "unexpected %s seq %u, should be >= %u\n",
>  			     es->name, es->current_seq, es->last_seq);
> -		igt_assert_f(es->current_seq - es->last_seq <= 100,
> +		igt_assert_f(es->current_seq - es->last_seq <= 150,
>  			     "unexpected %s seq %u, should be < %u\n",
> -			     es->name, es->current_seq, es->last_seq + 100);
> +			     es->name, es->current_seq, es->last_seq + 150);
>  
>  		igt_debug("testing ts continuity: Current frame %u, old frame %u\n",
>  			  es->current_seq, es->last_seq);
> -- 
> 2.4.10
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch


More information about the Intel-gfx mailing list