public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Mika Kahola <mika.kahola@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 5/5] tests/kms_test_only: Validate TEST_ONLY correctness against full atomic commit
Date: Thu, 12 Jan 2017 11:11:45 +0100	[thread overview]
Message-ID: <bc28b7c3-8c94-35e8-8fdb-ec6ee3eb90e4@linux.intel.com> (raw)
In-Reply-To: <1483099241-15898-6-git-send-email-mika.kahola@intel.com>

Op 30-12-16 om 13:00 schreef Mika Kahola:
> This test case adds TEST_ONLY flag to the following test cases to test
> atomic commit correctness.
>
>  - kms_plane_multiple
>  - kms_atomic_transitions
>  - kms_plane_scaling
>  - kms_rotation_crc
>
> The test randomly selects one of the above test cases and tests atomic
> commit. If the test fails with TEST_ONLY flag the real deal atomic commit
> is executed and the outcome is verified.
>
> The test runs by default for 64 iterations.
>
> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> ---
>  tests/Makefile.sources |   1 +
>  tests/kms_test_only.c  | 455 +++++++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 456 insertions(+)
>  create mode 100644 tests/kms_test_only.c
Hey,

What does this test add?

Any test should pass with PASS. This test retrying failed test-only tests won't add much there. No test should ever fail.

~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-01-12 10:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-30 12:00 [PATCH i-g-t 0/5] Validate TEST_ONLY correctness against full atomic commit Mika Kahola
2016-12-30 12:00 ` [PATCH i-g-t 1/5] tests/kms_plane_multiple: Add TEST_ONLY flag Mika Kahola
2017-01-12 13:45   ` Maarten Lankhorst
2016-12-30 12:00 ` [PATCH i-g-t 2/5] tests/kms_atomic_transition: " Mika Kahola
2016-12-30 12:00 ` [PATCH i-g-t 3/5] tests/kms_plane_scaling: " Mika Kahola
2016-12-30 12:00 ` [PATCH i-g-t 4/5] tests/kms_rotation_crc: " Mika Kahola
2016-12-30 12:00 ` [PATCH i-g-t 5/5] tests/kms_test_only: Validate TEST_ONLY correctness against full atomic commit Mika Kahola
2017-01-12 10:11   ` Maarten Lankhorst [this message]
     [not found]     ` <1484216887.9014.8.camel@intel.com>
2017-01-12 11:37       ` Maarten Lankhorst
2017-01-23 13:26         ` Mika Kahola
2017-01-23 15:35           ` Maarten Lankhorst

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=bc28b7c3-8c94-35e8-8fdb-ec6ee3eb90e4@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kahola@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