Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
Cc: igt-dev@lists.freedesktop.org, petri.latvala@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_color: fix crc assert condition
Date: Wed, 21 Sep 2022 10:47:56 +0300	[thread overview]
Message-ID: <YyrBrDSeogdOq4zs@intel.com> (raw)
In-Reply-To: <9c8f18bc-a815-84a0-93eb-698a4083bbe0@intel.com>

On Tue, Sep 20, 2022 at 03:32:39PM +0530, Modem, Bhanuprakash wrote:
> On Mon-19-09-2022 09:24 pm, Melissa Wen wrote:
> > On 09/01, Modem, Bhanuprakash wrote:
> >> On Wed-31-08-2022 03:41 pm, Melissa Wen wrote:
> >>> In test_pipe_degamma/gamma/ctm, igt_assert_crc_equal() was replaced by
> >>>
> >>> ret = !igt_skip_crc_compare || igt_check_crc_equal()
> >>> and then igt_assert(ret)
> >>>
> >>> where igt_check_crc_equal returns !mismatch, and therefore we can
> >>> translate as:
> >>>
> >>> ret = !igt_skip_crc_compare || !mismatch
> >>>
> >>> However, the original igt_assert_crc_equal() assertion does:
> >>>
> >>> igt_assert(!mismatch || igt_skip_crc_compare)
> >>>
> >>> That means, the replacement changes the original assertion. Moreover,
> >>> negating `igt_skip_crc_compare` makes the test assertion to be always
> >>> true (sucessful) by default and reverses the logic of
> >>> --skip-crc-compare.
> >>>
> >>> Fixes: d61e4598142 ("tests/kms_color: Convert tests to dynamic")
> >>> Signed-off-by: Melissa Wen <mwen@igalia.com>
> >>
> >> LGTM
> >> Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> >>
> >> - Bhanu
> > 
> > Thanks for reviewing, Bhanu.
> > 
> > Siqueira,
> > 
> > Is it okay from AMD side? If so, can you apply it?
> 
> Applied.

It did _not_ pass CI and so should not have been pushed!

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2022-09-21  7:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 10:11 [igt-dev] [PATCH i-g-t] tests/kms_color: fix crc assert condition Melissa Wen
2022-08-31 11:03 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-08-31 17:36 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-09-01  9:15 ` [igt-dev] [PATCH i-g-t] " Modem, Bhanuprakash
2022-09-19 15:54   ` Melissa Wen
2022-09-20 10:02     ` Modem, Bhanuprakash
2022-09-21  7:47       ` Ville Syrjälä [this message]
2022-09-21 10:36         ` Melissa Wen
2022-09-21 10:50           ` Ville Syrjälä
2022-09-21 15:54             ` Modem, Bhanuprakash
2022-09-21 16:43               ` Ville Syrjälä
2022-09-21 17:31                 ` Melissa Wen
2022-09-22  5:31                   ` Modem, Bhanuprakash

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=YyrBrDSeogdOq4zs@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@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