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

Issue 795585 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

system_health.common_desktop failing on multiple builders

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 17 2017

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of oysteine@google.com

system_health.common_desktop failing on multiple builders

Builders failed on: 
- Mac Pro 10.11 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Mac%20Pro%2010.11%20Perf
- Win 10 High-DPI Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%2010%20High-DPI%20Perf


 
Cc: -oysteine@google.com nednguyen@chromium.org
Owner: oysteine@chromium.org
Seems to be mainly load:media:youtube failing due to:

Traceback (most recent call last):
  File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/value/failure.py", line 41, in _GetExcInfoFromMessage
    raise Exception(message)
Exception: Error: The sliding window must fit in the specified time range
    at Object.maxExpectedQueueingTimeInSlidingWindow (/tracing/extras/chrome/estimated_input_latency.html:308:13)
    at addExpectedQueueingTimeMetric_ (/tracing/metrics/system_health/expected_queueing_time_metric.html:139:23)
    at new expectedQueueingTimeMetric (/tracing/metrics/system_health/expected_queueing_time_metric.html:85:5)
    at runMetrics (/b/s/w/ir/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:47:16)
    at metricMapFunction (/b/s/w/ir/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:149:24)
    at Object.mapSingleTrace (/tracing/mre/map_single_trace.html:39:7)
    at eval (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:61:18)
    at Object.runAndConvertErrorsToFailures (/tracing/mre/map_single_trace.html:24:10)
    at mapSingleTraceWithResult (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:52:12)
    at Object.mapSingleTraceMain (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:77:20)

Example:
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%20Pro%2010.11%20Perf/builds/1866
https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FMac_Pro_10.11_Perf%2F1866%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.common_desktop_on_ATI_GPU_on_Mac_on_Mac-10.11%2F0%2Fstdout

Going to disable.
Disabling that story on Mac, specifically; looks like Win is a different issue.
Cc: tdres...@chromium.org
Project Member

Comment 4 by bugdroid1@chromium.org, Dec 17 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/acf6a9183353281a4c8b473d50d714dbdef41a6e

commit acf6a9183353281a4c8b473d50d714dbdef41a6e
Author: Oystein Eftevaag <oysteine@chromium.org>
Date: Sun Dec 17 13:35:19 2017

Disable system_health.desktop_common load:media:youtube on mac

TBR=nednguyen@chromium.org
BUG= 795585 

Change-Id: Idbe16201235a53ad7669478d58611708e607d5bc
Reviewed-on: https://chromium-review.googlesource.com/831508
Reviewed-by: oysteine <oysteine@chromium.org>
Commit-Queue: oysteine <oysteine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524622}
[modify] https://crrev.com/acf6a9183353281a4c8b473d50d714dbdef41a6e/tools/perf/page_sets/system_health/expectations.py

Cc: -nednguyen@chromium.org
Owner: nednguyen@chromium.org
Owner: nedngu...@google.com
Cc: dtu@chromium.org
Dave: how do I kick off the bisect on this?
Owner: u...@chromium.org
Status: Assigned (was: Available)
Since this is a metric crash, reassign this to Ulan who implemented this metric.
Components: Speed>Metrics
Cc: dproy@chromium.org

Comment 11 by dproy@google.com, Jan 10 2018

Is the EQT exception still an issue after https://chromium-review.googlesource.com/c/catapult/+/852827?

I looked at the most recent build on the waterfall. It seemed to me that we're not getting the expected queueing time metric error anymore, but there are other exceptions that's causing the current failure. An example warning message is "WARNING:root:task_output_dir '/var/folders/9x/6c6sv3cj4j53wzpzthbp4ksm0000gm/T/tmpdXVAsb' already exists!" followed by 

| End of shard 0                                                         
|  Pending: 36037.3s  EXPIRED (lack of capacity)                   

Comment 12 by maxlg@chromium.org, Apr 23 2018

Is there any update for this bug?

Comment 13 by dproy@chromium.org, Apr 23 2018

Cc: nednguyen@chromium.org
I think the build is fine now but +Ned for confirmation before closing this. 

Comment 14 by u...@chromium.org, Apr 23 2018

Sorry, I missed this bug. The fix in comment #11 looks good.
Cc: u...@chromium.org
Owner: dproy@chromium.org
Status: Fixed (was: Assigned)
Looks like this is fixed to me. Mark dproy@ as owner since it was https://chromium-review.googlesource.com/c/catapult/+/852827 which fixed it

Sign in to add a comment