New issue
Advanced search Search tips

Issue 732528 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Turn off buildbot 'silence' build killing feature?

Project Member Reported by dgarr...@chromium.org, Jun 12 2017

Issue description

It might be useful to stop killing builds that go for too long without logging anything, since we have build timeout, and this 'quiet logging' timeout will go away when we move to swarming.

We have been having issues with lab tests that pass despite > 2.5 hours of quiet. There are supposed to be keep alive logs, but they appear to be being buffered. In group discussion we thought it might be faster to just turn off the 'quiet' killer.
 

Comment 1 by d...@chromium.org, Jun 13 2017

Owner: dgarr...@chromium.org
"and this 'quiet logging' timeout will go away when we move to swarming." Swarming has an I/O timeout, so I don't think it will unless you explicitly make this the case.

The I/O timeout can be adjusted; recommend just picking a point that works :)
Status: Assigned (was: Untriaged)
My 2 cents: This I/O timeout is meant to blow away anything that's entirely stuck. In that case the assumption is that none of the cbuildbot timeouts will work (cbuildbot is hung).
Buildbucket timeouts may still work.

That said, going silent for long periods on the build is bad on its own -- users have no idea what's happening.

dgarrett, I'd suggest : drop this request. Handle the root cause (issue 730729) of the observed failure instead.
Status: WontFix (was: Assigned)
Yeah, I think I agree, especially since swarming has the same feature.
Issue 732868 has been merged into this issue.

Sign in to add a comment