From: "José Roberto de Souza" <jose.souza@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] tests/kms_psr2_su: Print the SU blocks mismatches
Date: Thu, 23 Jan 2020 11:00:29 -0800 [thread overview]
Message-ID: <20200123190029.19882-1-jose.souza@intel.com> (raw)
This will help us debug failures in this test.
Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
---
tests/kms_psr2_su.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tests/kms_psr2_su.c b/tests/kms_psr2_su.c
index f2244b29..9f40c735 100644
--- a/tests/kms_psr2_su.c
+++ b/tests/kms_psr2_su.c
@@ -183,9 +183,13 @@ static bool update_screen_and_test(data_t *data)
igt_assert_f(data->op, "Operation not handled\n");
}
- if (psr2_wait_su(data->debugfs_fd, &su_blocks))
+ if (psr2_wait_su(data->debugfs_fd, &su_blocks)) {
ret = su_blocks == EXPECTED_NUM_SU_BLOCKS;
+ if (!ret)
+ igt_debug("Not matching SU blocks read: %u\n", su_blocks);
+ }
+
return ret;
}
@@ -206,7 +210,6 @@ static void run(data_t *data)
result = update_screen_and_test(data);
}
- igt_debug("Screen changes: %u\n", data->screen_changes);
igt_assert_f(result,
"No matching selective update blocks read from debugfs\n");
}
--
2.25.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-01-23 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 19:00 José Roberto de Souza [this message]
2020-01-23 20:24 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_psr2_su: Print the SU blocks mismatches Patchwork
2020-01-25 8:25 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2020-02-24 5:18 ` [igt-dev] [PATCH i-g-t] " Anshuman Gupta
2020-02-24 23:17 ` Souza, Jose
2020-02-25 4:00 ` Anshuman Gupta
2020-02-25 18:17 ` Souza, Jose
2020-02-26 7:44 ` Anshuman Gupta
2020-02-26 20:27 ` Souza, Jose
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=20200123190029.19882-1-jose.souza@intel.com \
--to=jose.souza@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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