New issue
Advanced search Search tips

Issue 670867 link

Starred by 3 users
Status: Archived
Owner: ----
Closed: May 2018
Cc:
no...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

bot_update stuck in 427 hours on Mac before it was manually killed

Project Member Reported by kjellander@chromium.org, Dec 2 2016 
I wonder how this is possible: https://build.chromium.org/p/chromium.webrtc/builders/Mac%20Builder/builds/60817

Why doesn't buildbot kill the build in this case? I thought even if the step keeps producing output, there's still some hard maximum timeout?

Comment 1 by kjellander@chromium.org, Feb 6 2017

Labels: -Type-Bug OS-Mac Type-Bug-Regression
Summary: bot_update stuck in 427 hours on Mac before it was manually killed (was: bot_update ran for 74 hours before I killed it)
Here's another build on another bot that got stuck in bot_update for 427 hours:
https://build.chromium.org/p/chromium.webrtc.fyi/builders/Mac%20Builder/builds/21471

How is this possible? I thought we had timeouts for all steps that were enforced?

Comment 2 by shrike@chromium.org, Mar 25 2017

Status: Available (was: Untriaged)
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 6 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by estaab@chromium.org, May 3 2018

Status: Archived (was: Untriaged)
►

Sign in to add a comment