[Intel-gfx] [PATCH i-g-t] kms_atomic_transition: Output more finegrained progress info to avoid CI watchdog timeout

Petri Latvala petri.latvala at intel.com
Wed Oct 18 11:57:49 UTC 2017



On 10/18/2017 02:50 PM, Imre Deak wrote:
> On Wed, Oct 18, 2017 at 02:47:17PM +0300, Imre Deak wrote:
>> On Wed, Oct 18, 2017 at 02:43:38PM +0300, Petri Latvala wrote:
>>> On Wed, Oct 18, 2017 at 02:29:33PM +0300, Imre Deak wrote:
>>>> The CI software watchdog (owatch) will timeout if the test doesn't
>>>> output anything for a long time on standard out or error. At least the
>>>> plane-all-modeset-transition and plane-all-modeset-transition-fences
>>>> subtests run without any output longer than the watchdog timeout, so
>>>> output some more progress info.
>>> No, owatch is wrapping piglit, and pings the watchdog if _piglit_
>>> prints anything. Which it does on start/exit of a test.
>> Yes, but the subtest itself takes more time than owatch's timeout,
>> during which there is no output. So owatch will trigger a reboot before
>> the subtest ends, even though it's making progress.
> Or you mean piglit doesn't forward the test's stdout, stderr? In that
> case this won't work.

Yeah, sorry I was too terse. Piglit redirects the test output (out and 
err) to its own files. Printing from the test does not trigger owatch's 
heartbeat.

-- 
Petri Latvala



More information about the Intel-gfx mailing list