public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ser, Simon" <simon.ser@intel.com>
To: "martin.peres@linux.intel.com" <martin.peres@linux.intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v3] tests/kms_flip: improve logging when timing out
Date: Tue, 25 Jun 2019 11:27:52 +0000	[thread overview]
Message-ID: <186a3ffbc30e6390f5557ffa86192a98f28c6e5c.camel@intel.com> (raw)
In-Reply-To: <56f4170d6f1b37e8bd273fd779636337c01e7374.camel@intel.com>

On Mon, 2019-06-24 at 12:44 +0000, Ser, Simon wrote:
> On Mon, 2019-06-24 at 15:00 +0300, Arkadiusz Hiler wrote:
> > On Mon, Jun 24, 2019 at 11:28:22AM +0300, Simon Ser wrote:
> > > Signed-off-by: Simon Ser <simon.ser@intel.com>
> > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105363
> > Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> > 
> > Please make sure that filters are updated before merging.
> 
> Martin, can you update the filters of that issue to include:
> 
>     igt_assert(end - start < 500);

Arek taught me how to do it in the end :)

> Thanks
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2019-06-25 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24  8:28 [igt-dev] [PATCH i-g-t v3] tests/kms_flip: improve logging when timing out Simon Ser
2019-06-24  8:59 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_flip: improve logging when timing out (rev3) Patchwork
2019-06-24 10:13 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-06-24 12:00 ` [igt-dev] [PATCH i-g-t v3] tests/kms_flip: improve logging when timing out Arkadiusz Hiler
2019-06-24 12:44   ` Ser, Simon
2019-06-25 11:27     ` Ser, Simon [this message]

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=186a3ffbc30e6390f5557ffa86192a98f28c6e5c.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=martin.peres@linux.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