From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t V2 8/8] tests/kms_color: Fix crc compare check in CTM tests
Date: Thu, 22 Sep 2022 08:49:50 +0300 [thread overview]
Message-ID: <Yyv3fowHUEsbY9cN@intel.com> (raw)
In-Reply-To: <20220922051142.2003118-9-bhanuprakash.modem@intel.com>
On Thu, Sep 22, 2022 at 10:41:42AM +0530, Bhanuprakash Modem wrote:
> !igt_skip_crc_compare || igt_check_crc_equal() is always true
> which is not correct.
>
> Fixes: 1a42910d
Hang on. Now you're saying the regression in detecting actual failures
was introduced in commit 1a42910d4f8b ("tests/kms_color: Don't opencode
igt_check_crc_equal()") rather than the dynamic subtest conversion
commit (which is what the previous Fixes line claimed)?
So apparently the test may have been broken for 1.5 years now and
no one realize it.
Hmm. And idea just came to me. Could we introduce some kind of fairly
generic (say, igt_fb level) knob that would attempt to introduce a real
crc mismatch into all (or at least most) tests? Eg. maybe igt_fb could
frob around with the pixels a bit or something? This would at least
allow one to easily verify that the test *may* start to fail when
turning that knob on. Whether it actually starts to fail for a given
pixel frobbry isn't 100% guaraneed though since we could just end up
with a crc collision by dumb luck. Ideally we would have some way to
guarantee the failure, and then we would just make CI run every test
a second time with knob turned on to validate that the test can
actually detect the failure. But maybe this is a pipe dream.
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> ---
> tests/kms_color.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/kms_color.c b/tests/kms_color.c
> index ba06947b..e2462aa3 100644
> --- a/tests/kms_color.c
> +++ b/tests/kms_color.c
> @@ -510,7 +510,7 @@ static bool test_pipe_ctm(data_t *data,
> /* Verify that the CRC of the software computed output is
> * equal to the CRC of the CTM matrix transformation output.
> */
> - ret &= !igt_skip_crc_compare || igt_check_crc_equal(&crc_software, &crc_hardware);
> + ret = igt_skip_crc_compare || igt_check_crc_equal(&crc_software, &crc_hardware);
>
> igt_plane_set_fb(primary, NULL);
> igt_output_set_pipe(output, PIPE_NONE);
> --
> 2.37.3
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-09-22 5:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 5:11 [igt-dev] [i-g-t V2 0/8] Revert Color patches Bhanuprakash Modem
2022-09-22 5:11 ` [igt-dev] [i-g-t V2 1/8] Revert "tests/kms_color: fix crc assert condition" Bhanuprakash Modem
2022-09-22 5:11 ` [igt-dev] [i-g-t V2 2/8] Revert "tests/kms: Fix to use max_bpc constraint helper" Bhanuprakash Modem
2022-09-22 5:11 ` [igt-dev] [i-g-t V2 3/8] Revert "tests/kms_color: Fix multiple failures in deep-color tests" Bhanuprakash Modem
2022-09-22 5:11 ` [igt-dev] [i-g-t V2 4/8] Revert "tests/kms_color: Fix memory leaks" Bhanuprakash Modem
2022-09-22 5:11 ` [igt-dev] [i-g-t V2 5/8] Revert "tests/kms_color: Test Cleanup" Bhanuprakash Modem
2022-09-22 5:11 ` [igt-dev] [i-g-t V2 6/8] Revert "tests/kms_color: Convert tests to dynamic" Bhanuprakash Modem
2022-09-22 5:11 ` [igt-dev] [i-g-t V2 7/8] Revert "tests/kms_color_chamelium: " Bhanuprakash Modem
2022-09-22 5:11 ` [igt-dev] [i-g-t V2 8/8] tests/kms_color: Fix crc compare check in CTM tests Bhanuprakash Modem
2022-09-22 5:49 ` Ville Syrjälä [this message]
2022-09-22 6:18 ` Ville Syrjälä
2022-09-22 10:25 ` Petri Latvala
2022-09-22 19:06 ` Lyude Paul
2022-09-22 19:40 ` Ville Syrjälä
2022-09-25 11:46 ` Modem, Bhanuprakash
2022-09-22 15:28 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Revert Color patches Patchwork
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=Yyv3fowHUEsbY9cN@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=bhanuprakash.modem@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