New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 707095 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: May 2017
Cc:
charliea@chromium.org
█ rnep...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

battor.steady_state.reference took 1hr 6 minutes to fail

Project Member Reported by nedngu...@google.com, Mar 31 2017 
The non reference version took only 4 minutes to run.

https://build.chromium.org/p/chromium.perf/builders/Mac%20Retina%20Perf/builds/485

We should figure out what step is not timed out properly here. This is a big risk when  issue 680138  is fixed.

Comment 1 by charliea@chromium.org, Mar 31 2017 

rnephew@, can you work on looking at the serial log and, if necessary, routing this to the Mellow folks for investigation?

Comment 2 by nedngu...@google.com, Mar 31 2017 

Whichever method that was hang in Python should also have a timed out.

Comment 3 by charliea@chromium.org, May 4 2017 

Has there been any investigation into what might have been responsible for this? Have we seen it again and, if not, should we close this as WontFix?

Comment 4 by rnep...@chromium.org, May 4 2017 

Oh wow, I completely missed this bug. Sorry. Yes I think this is still an issue. 
 crbug.com/718366  is possibly a dupe of this.

Comment 5 by nedngu...@google.com, May 4 2017

Status: WontFix (was: Untriaged)
The runtime seems stable now. I guess we can reopen the bug when we see this happens again.

https://chromeperf.appspot.com/report?sid=cc240271665116d44707eb3601969d8009c7c484e952a504f42a774a3653f735
►

Sign in to add a comment