public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ser, Simon" <simon.ser@intel.com>
To: "Hiler, Arkadiusz" <arkadiusz.hiler@intel.com>,
	"Latvala, Petri" <petri.latvala@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Sarvela, Tomi P" <tomi.p.sarvela@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/2 v2] runner: Add support for aborting on network failure
Date: Mon, 20 May 2019 06:30:15 +0000	[thread overview]
Message-ID: <1106b240f422afee1656cc6141afe4af1ca63928.camel@intel.com> (raw)
In-Reply-To: <20190520061758.7obtf6gfwhgy2brb@ahiler-desk1.fi.intel.com>

On Mon, 2019-05-20 at 09:17 +0300, Arkadiusz Hiler wrote:
> On Thu, May 16, 2019 at 02:27:54PM +0300, Petri Latvala wrote:
> > If the network goes down while testing, CI tends to interpret that as
> > the device being down, cutting its power after a while. This causes an
> > incomplete to an innocent test, increasing noise in the results.
> > 
> > A new flag to --abort-on-monitored-error, "ping", uses liboping to
> > ping a host configured in .igtrc with one ping after each test
> > execution and aborts the run if there is no reply in a hardcoded
> > amount of time.
> > 
> > v2:
> >  - Use a higher timeout
> >  - Allow hostname configuration from environment
> > 
> > Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> > Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> > Cc: Martin Peres <martin.peres@linux.intel.com>
> > Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
> > ---
> >  meson.build        |   1 +
> >  meson_options.txt  |   6 ++
> >  runner/executor.c  | 135 +++++++++++++++++++++++++++++++++++++++++++++
> >  runner/meson.build |  12 +++-
> >  runner/settings.c  |   4 ++
> >  runner/settings.h  |   5 +-
> >  6 files changed, 160 insertions(+), 3 deletions(-)
> > 
> > diff --git a/meson.build b/meson.build
> > index a05e912c..aac67f1a 100644
> > --- a/meson.build
> > +++ b/meson.build
> > @@ -100,6 +100,7 @@ build_tests = get_option('build_tests')
> >  with_libdrm = get_option('with_libdrm')
> >  with_libunwind = get_option('with_libunwind')
> >  build_runner = get_option('build_runner')
> > +with_oping = get_option('with_oping')
> 
> I find it a bit distracting that we have this bit here, whereas
> everything else is in runner/meson.build. Is there any reason for that?
> 
> >  _build_overlay = build_overlay != 'false'
> >  _overlay_required = build_overlay == 'true'
> <SNIP>
> > diff --git a/runner/meson.build b/runner/meson.build
> > index b658f1d2..a54aaab4 100644
> > --- a/runner/meson.build
> > +++ b/runner/meson.build
> > @@ -1,4 +1,13 @@
> >  jsonc = dependency('json-c', required: _runner_required)
> > +runner_deps = [jsonc, glib]
> > +have_oping = []
> > +if with_oping != 'false'
> > +	oping = dependency('liboping', required: with_oping == 'true')
> > +	if oping.found()
> > +		runner_deps += oping
> > +		have_oping = '-DHAVE_OPING=1'
> > +	endif
> > +endif
> 
> I think it is about time to:
> https://mesonbuild.com/Release-notes-for-0-47-0.html#new-type-of-build-option-for-features
> 
> I'll check meson versions in various popular distros Today and see how
> the patch would look like.

Oh, +1 from me!

I'd really like to replace some complicated logic with feature options.

> >  runnerlib_sources = [ 'settings.c',
> >  		      'job_list.c',
> > @@ -21,7 +30,8 @@ if _build_runner and _build_tests and jsonc.found()
> >  
> >  	runnerlib = static_library('igt_runner', runnerlib_sources,
> >  				   include_directories : inc,
> > -				   dependencies : [jsonc, glib])
> > +				   c_args : have_oping,
> 
> I know that we have just a single dep here, but can we name this
> runner_lib_c_args or something?
> 
> > +				   dependencies : runner_deps)
> >  
> >  	runner = executable('igt_runner', runner_sources,
> >  			    link_with : runnerlib,
> 
> Other than that the C part looks ok. I share Daniel's sentiment on
> network and NIC possibly being be a bit too "best-efforty" for aborting
> on a single dropped ping.
> 
> It also seems like the feature haven't been properly tested, as the HAX
> does not specify any IP address.
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-05-20  6:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 11:27 [igt-dev] [PATCH i-g-t 1/2 v2] runner: Add support for aborting on network failure Petri Latvala
2019-05-16 11:27 ` [igt-dev] [PATCH i-g-t 2/2] HAX: Check all conditions to abort Petri Latvala
2019-05-16 12:23 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2,v2] runner: Add support for aborting on network failure Patchwork
2019-05-16 12:51 ` [igt-dev] [PATCH i-g-t 1/2 v2] " Daniel Vetter
2019-05-16 14:45 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/2,v2] " Patchwork
2019-05-20  6:17 ` [igt-dev] [PATCH i-g-t 1/2 v2] " Arkadiusz Hiler
2019-05-20  6:30   ` Ser, Simon [this message]
2019-05-20  9:36   ` Petri Latvala

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=1106b240f422afee1656cc6141afe4af1ca63928.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    --cc=tomi.p.sarvela@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