Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kunal Joshi <kunal1.joshi@intel.com>
To: Martin Peres <martin.peres@linux.intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/igt_chamelium.c: Skip test if chamelium
Date: Fri, 13 Dec 2019 15:27:17 +0530	[thread overview]
Message-ID: <20191213095717.GA5202@intel.com> (raw)
In-Reply-To: <d37b7955-53e3-8d02-25b6-cf5255fece76@linux.intel.com>

On 2019-12-12 at 17:37:45 +0530, Martin Peres wrote:
> On 12/12/2019 13:26, Kunal Joshi wrote:
> > If chamelium is not present at the specified IP in the igtrc file,
> > tests should be skipped instead of failing.
> > Adding a change to skip tests on any network related issue and
> > assert on any other issue.
> > 
> > Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
> > ---
> >  lib/igt_chamelium.c | 9 ++++++---
> >  1 file changed, 6 insertions(+), 3 deletions(-)
> > 
> > diff --git a/lib/igt_chamelium.c b/lib/igt_chamelium.c
> > index 9971f51..79eddde 100644
> > --- a/lib/igt_chamelium.c
> > +++ b/lib/igt_chamelium.c
> > @@ -344,9 +344,12 @@ static xmlrpc_value *chamelium_rpc(struct chamelium *chamelium,
> >  				 format_str, va_args);
> >  	va_end(va_args);
> >  
> > -	igt_assert_f(!chamelium->env.fault_occurred,
> > -		     "Chamelium RPC call failed: %s\n",
> > -		     chamelium->env.fault_string);
> > +	if (chamelium->env.fault_code == XMLRPC_NETWORK_ERROR)
> > +		igt_skip("Chamelium not found at specified IP");
> 
> This message is misleading when the network just did not come back.
> 
> I prefer the fact that the test fails as it draws attention to either a
> mis-configured igtrc, a network problem, or a chamelium problem.
> 
Would it be fine if I modify the log to state the cause more explicitly?
Would you also suggest waiting for the xml-rpc timeout, to assure that
the problem isn't with network not coming back?
Is there a better way I can handle this?
> What is your rationale for this change? Skips are considered as failure
> anyway from our bug tracking point of view.
> 
If we happen to use igt_chamelium library with some other tests, then
skipping could be more appropriate than failing?
For Ex: In PSR tests we skip the test if edp panel is not present rather
than failing.
The same way I think the test should be skipped if chamelium is not
present.
> Martin
> 
> > +	else
> > +		igt_assert_f(!chamelium->env.fault_occurred,
> > +				"Chamelium RPC call failed: %s\n",
> > +				chamelium->env.fault_string);
> >  
> >  	return res;
> >  }
> > 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-12-13  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 11:26 [igt-dev] [PATCH i-g-t] lib/igt_chamelium.c: Skip test if chamelium Kunal Joshi
2019-12-12 12:07 ` Martin Peres
2019-12-13  9:57   ` Kunal Joshi [this message]
2019-12-16 11:17     ` Martin Peres
2019-12-12 12:18 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-12-13  0:49 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20191213095717.GA5202@intel.com \
    --to=kunal1.joshi@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=martin.peres@linux.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