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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

tbh this sounds like owatch being dense and it shouldn't try to reboot
this quickly. What's the current owatch timeout?

Aside: What exactly does owatch give us? I thought jenkins also watches
machines and reboots them using the ac switch ... And owatch provides
spurious reboots?
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux