All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manasi Navare <manasi.d.navare@intel.com>
To: Antonio Argenziano <antonio.argenziano@intel.com>,
	igt-dev@lists.freedesktop.org,
	Anusha Srivatsa <anusha.srivatsa@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] test/kms_dp_dsc: Basic KMS test to validate VESA DSC on DP/eDP
Date: Wed, 17 Oct 2018 09:01:03 -0700	[thread overview]
Message-ID: <20181017160102.GA8968@intel.com> (raw)
In-Reply-To: <20181017074824.GO17124@platvala-desk.ger.corp.intel.com>

On Wed, Oct 17, 2018 at 10:48:24AM +0300, Petri Latvala wrote:
> On Tue, Oct 16, 2018 at 02:14:59PM -0700, Antonio Argenziano wrote:
> > > > > +		igt_assert_eq(ret, 0);
> > > > > +	}
> > > > > +
> > > > > +	close(drm_fd);
> > > > > +
> > > > > +	igt_assert_eq(ret, 0);
> > > > 
> > > > 'ret' is already checked in the subtest also, this would fail if you don't
> > > > run the subtest.
> > > 
> > > If I dont run the subtest, it will use the initialized value of ret which is 0.
> > > It will only fail if update_display returns a negative value.
> > 
> > Sorry, you are right I misread that. But, it will not be this assert to fire
> > if ret != 0 but the one in the subtest. My point was that this statement
> > seems a bit redundant and could be eliminated.
> 
> It's not only redundant, it's invalid to call igt_assert when not
> inside an igt_fixture or a subtest. See lib/igt_core.c:1180,
> igt_can_fail().
>

Thanks Antonio and Petri for pointing this out.
I will remove the igt_assert from there. The igt_fixture() should already take care
of having that after the test right? So I dont need to call it explicitly in igt_fixture()

Manasi 
> 
> 
> -- 
> Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2018-10-17 16:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 23:34 [igt-dev] [PATCH i-g-t] test/kms_dp_dsc: Basic KMS test to validate VESA DSC on DP/eDP Manasi Navare
2018-10-06  1:53 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-10-06 10:14 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-10-10 15:48 ` [igt-dev] [PATCH i-g-t] " Antonio Argenziano
2018-10-16 18:47   ` Manasi Navare
2018-10-16 21:14     ` Antonio Argenziano
2018-10-16 21:37       ` Manasi Navare
2018-10-17 20:38         ` Antonio Argenziano
2018-10-26 23:28           ` Manasi Navare
2018-10-17  7:48       ` Petri Latvala
2018-10-17 16:01         ` Manasi Navare [this message]
2018-10-17 16:49           ` Antonio Argenziano
2018-10-20  0:06             ` Manasi Navare
2018-10-11 21:21 ` Radhakrishna Sripada
2018-10-12  7:20   ` Radhakrishna Sripada
2018-10-16 19:11   ` Manasi Navare
2018-11-02 22:39 ` Dhinakaran Pandiyan
2018-11-05 20:58   ` Manasi Navare
2018-11-05 23:22     ` Dhinakaran Pandiyan
2018-11-06  0:29       ` Manasi Navare
  -- strict thread matches above, loose matches on Subject: below --
2018-12-13  0:57 Anusha
2018-12-17 12:00 ` Petri Latvala
2018-12-17 19:44   ` Srivatsa, Anusha
2018-12-18 12:12     ` Petri Latvala
2018-12-20 19:09       ` Srivatsa, Anusha
2018-12-20 19:10 Anusha
2018-12-21 12:14 ` Petri Latvala
2018-12-21 16:57   ` Manasi Navare

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=20181017160102.GA8968@intel.com \
    --to=manasi.d.navare@intel.com \
    --cc=antonio.argenziano@intel.com \
    --cc=anusha.srivatsa@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 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.