public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 2/8] kms_frontbuffer_tracking: Skip on unreliable CRC.
Date: Thu, 3 Dec 2015 08:50:00 +0100	[thread overview]
Message-ID: <20151203075000.GE10243@phenom.ffwll.local> (raw)
In-Reply-To: <1446749614-6606-2-git-send-email-rodrigo.vivi@intel.com>

On Thu, Nov 05, 2015 at 10:53:28AM -0800, Rodrigo Vivi wrote:
> Even with all sink crc re-works we still have platforms
> where after 6 vblanks it is unable to calculate the
> sink crc. But if we don't get the sink crc it isn't true
> that test failed, but that we have no ways to say test
> passed or failed.
> 
> So let's print a message and move forward in case sink crc
> cannot help us to know if the screen has been updated.
> 
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  tests/kms_frontbuffer_tracking.c | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/kms_frontbuffer_tracking.c b/tests/kms_frontbuffer_tracking.c
> index cd2879d..606d0a9 100644
> --- a/tests/kms_frontbuffer_tracking.c
> +++ b/tests/kms_frontbuffer_tracking.c
> @@ -858,10 +858,17 @@ static bool psr_wait_until_enabled(void)
>  
>  static void get_sink_crc(sink_crc_t *crc)
>  {
> +	int rc, errno_;
> +
>  	lseek(sink_crc.fd, 0, SEEK_SET);
>  
> -	igt_assert(read(sink_crc.fd, crc->data, SINK_CRC_SIZE) ==
> -		   SINK_CRC_SIZE);
> +	rc = read(sink_crc.fd, crc->data, SINK_CRC_SIZE);
> +	errno_ = errno;
> +
> +	if (rc == -1 && errno_ == ETIMEDOUT)
> +		igt_skip("Sink CRC is unreliable on this machine. Try running this test again individually\n");

igt_skip_on, just as an aside.
-Daniel

> +
> +	igt_assert(rc == SINK_CRC_SIZE);
>  }
>  
>  static bool sink_crc_equal(sink_crc_t *a, sink_crc_t *b)
> -- 
> 2.4.3
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2015-12-03  7:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 18:53 [PATCH i-g-t 1/8] kms_frontbuffer_tracking: Increase the time we wait for PSR Rodrigo Vivi
2015-11-05 18:53 ` [PATCH i-g-t 2/8] kms_frontbuffer_tracking: Skip on unreliable CRC Rodrigo Vivi
2015-11-05 20:30   ` Paulo Zanoni
2015-11-18 10:27     ` Daniel Vetter
2015-12-02  1:10     ` Rodrigo Vivi
2015-12-03  7:50   ` Daniel Vetter [this message]
2015-11-05 18:53 ` [PATCH i-g-t 3/8] kms_frontbuffer_tracking: Allow pipe crc or sink crc individually Rodrigo Vivi
2015-11-05 21:00   ` Paulo Zanoni
2015-11-05 18:53 ` [PATCH i-g-t 4/8] kms_frontbuffer_tracking: Allow to skip suspend_resume sub test case Rodrigo Vivi
2015-11-05 20:34   ` Paulo Zanoni
2015-11-05 20:40     ` Ville Syrjälä
2015-11-09 13:52       ` Paulo Zanoni
2015-11-18 10:31         ` Daniel Vetter
2015-11-05 18:53 ` [PATCH i-g-t 5/8] kms_frontbuffer_tracking: Add option to allow running tescases with PSR disabled Rodrigo Vivi
2015-11-05 20:44   ` Paulo Zanoni
2015-11-05 18:53 ` [PATCH i-g-t 6/8] kms_frontbuffer_tracking: Add option to allow running tescases with FBC disabled Rodrigo Vivi
2015-11-05 18:53 ` [PATCH i-g-t 7/8] kms_psr_sink_crc: Fix no-psr option Rodrigo Vivi
2015-11-05 18:53 ` [PATCH i-g-t 8/8] kms_psr_sink_crc: Add suspend/resume sub test Rodrigo Vivi
2015-11-05 20:11 ` [PATCH i-g-t 1/8] kms_frontbuffer_tracking: Increase the time we wait for PSR Paulo Zanoni
2015-12-02  1:19   ` Rodrigo Vivi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151203075000.GE10243@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox