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 07/10] tests/kms_psr_sink_crc: Use pressed key to pass/fail.
Date: Mon, 16 Mar 2015 10:04:28 +0100 [thread overview]
Message-ID: <20150316090428.GH21993@phenom.ffwll.local> (raw)
In-Reply-To: <1426285167-1260-7-git-send-email-rodrigo.vivi@intel.com>
On Fri, Mar 13, 2015 at 06:19:24PM -0400, Rodrigo Vivi wrote:
> This is useful when 1 person is running all tests and other one is reading log willing
> to know what tests passed and which failed. So tester is able to run all tests without
> stop and send log to developer.
>
> v2: Rebased after igt_debug_warn_and_wait_for_key
>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> tests/kms_psr_sink_crc.c | 20 +++++++++++++++-----
> 1 file changed, 15 insertions(+), 5 deletions(-)
>
> diff --git a/tests/kms_psr_sink_crc.c b/tests/kms_psr_sink_crc.c
> index 24f5ca8..ce50cdd 100644
> --- a/tests/kms_psr_sink_crc.c
> +++ b/tests/kms_psr_sink_crc.c
> @@ -316,11 +316,21 @@ static bool is_green(char *crc)
>
> static void assert_or_manual(bool condition, const char *expected)
> {
> - if (igt_interactive_debug)
> - igt_info("Is %s?\n", expected);
> - else
> - igt_debug("%s\n", expected);
> - igt_debug_wait_for_keypress("manual");
> + char msg[50];
> + char c;
> +
> + igt_debug("%s\n", expected);
> +
> + sprintf(msg, "Is %s [Y/n]? ", expected);
> + c = igt_debug_warn_and_wait_for_key("manual", msg);
> +
> + if (c) {
> + if (c == 'n' || c == 'N')
> + igt_fail(-1);
> + else
> + igt_info("\n");
> + }
Imo it'd be better to move this check into the helper too. And then give
it a name that makes it clear that it's a checkpoint for the user for
manual testing. I don't have any good ideas, but maybe
igt_interactive_debug_manual_check?
And imo you can fold this one in with the previous patch - easier to
understand if you add the user together with the function.
And one more aside: Should we document the different interactive debug
thigns somewhere?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-16 9:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 22:19 [PATCH i-g-t 01/10] tests/kms_psr_sink_crc: Make blt visible to human eyes Rodrigo Vivi
2015-03-13 22:19 ` [PATCH i-g-t 02/10] tests/kms_psr_sink_crc: Make render " Rodrigo Vivi
2015-03-16 8:59 ` Daniel Vetter
2015-03-16 20:23 ` Vivi, Rodrigo
2015-03-17 10:27 ` Daniel Vetter
2015-03-20 1:24 ` [PATCH] " Rodrigo Vivi
2015-03-20 9:54 ` Daniel Vetter
2015-03-20 17:43 ` Vivi, Rodrigo
2015-03-23 8:35 ` Daniel Vetter
2015-03-23 8:36 ` Daniel Vetter
2015-03-23 21:53 ` Vivi, Rodrigo
2015-03-24 9:02 ` Daniel Vetter
2015-04-15 1:08 ` Rodrigo Vivi
2015-03-13 22:19 ` [PATCH i-g-t 03/10] tests/kms_psr_sink_crc: Make mmaps " Rodrigo Vivi
2015-03-13 22:19 ` [PATCH i-g-t 04/10] tests/kms_psr_sink_crc: Make plane_move " Rodrigo Vivi
2015-03-13 22:19 ` [PATCH i-g-t 05/10] tests/kms_psr_sink_crc: Add manual mode Rodrigo Vivi
2015-03-13 22:19 ` [PATCH i-g-t 06/10] lib/igt_aux: Introduce igt_debug_warn_and_wait_for_key Rodrigo Vivi
2015-03-13 22:19 ` [PATCH i-g-t 07/10] tests/kms_psr_sink_crc: Use pressed key to pass/fail Rodrigo Vivi
2015-03-16 9:04 ` Daniel Vetter [this message]
2015-03-16 9:07 ` Daniel Vetter
2015-03-16 22:44 ` [PATCH] lib/igt_aux: Introduce igt_interactive_debug_manual_check Rodrigo Vivi
2015-03-17 10:28 ` Daniel Vetter
2015-03-20 1:11 ` Rodrigo Vivi
2015-03-20 9:55 ` Daniel Vetter
2015-03-13 22:19 ` [PATCH i-g-t 08/10] tests/kms_psr_sink_crc: remove timeout option from wait_psr_entry Rodrigo Vivi
2015-03-13 22:19 ` [PATCH i-g-t 09/10] test/kms_psr_sink_crc: Split plane setup operations Rodrigo Vivi
2015-03-13 22:19 ` [PATCH i-g-t 10/10] test/kms_psr_sink_crc: Add dpms off/on tests 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=20150316090428.GH21993@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.