From: Petri Latvala <petri.latvala@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] runner: Introduce per-test timeouts
Date: Tue, 18 Feb 2020 13:26:03 +0200 [thread overview]
Message-ID: <20200218112603.GP25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <158202145203.3043.6283843409560708384@skylake-alporthouse-com>
On Tue, Feb 18, 2020 at 10:24:12AM +0000, Chris Wilson wrote:
> Quoting Petri Latvala (2020-02-17 14:50:42)
> > A new config option, --per-test-timeout, sets a time a single test
> > cannot exceed without getting itself killed. The time resets when
> > starting a subtest or a dynamic subtest, so an execution with
> > --per-test-timeout=20 can indeed go over 20 seconds a long as it
> > launches a dynamic subtest within that time.
> >
> > As a bonus, verbose log level from runner now also prints dynamic
> > subtest begin/result.
> >
> > Signed-off-by: Petri Latvala <petri.latvala@intel.com>
>
> I wish igt had a pipe back to the runner so there was a clear protocol
> for this rather than trying to re-interpret the user output. (What's
> that you could pass commands from individual tests back to the runner,
> such as changing the dmesg filters, timeouts etc, etc)
Stop spying on my local branches.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-18 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 14:50 [igt-dev] [PATCH i-g-t 1/2] runner: Refactor timeouting Petri Latvala
2020-02-17 14:50 ` [igt-dev] [PATCH i-g-t 2/2] runner: Introduce per-test timeouts Petri Latvala
2020-02-18 10:24 ` Chris Wilson
2020-02-18 11:26 ` Petri Latvala [this message]
2020-02-17 16:47 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/2] runner: Refactor timeouting Patchwork
2020-02-18 11:29 ` Petri Latvala
2020-02-18 9:08 ` [igt-dev] [PATCH i-g-t 1/2] " Petri Latvala
2020-02-18 10:21 ` Chris Wilson
2020-02-18 15:38 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] " Patchwork
2020-02-19 7:09 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-02-19 10:39 ` 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=20200218112603.GP25209@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=chris@chris-wilson.co.uk \
--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