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

Issue 651384 link

Starred by 1 user
Status: Duplicate
Merged: issue 650306
Owner:
█ alexandermont@chromium.org
Last visit > 30 days ago
Closed: Sep 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

battor.power_cases_no_chrome_trace failing

Project Member Reported by skyos...@chromium.org, Sep 29 2016 
https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.perf%2FMac_Retina_Perf__4_%2F6208%2F%2B%2Frecipes%2Fsteps%2Fbattor.power_cases_no_chrome_trace%2F0%2Fstdout

MapFunctionError: Cannot read property 'rendererHelpers' of undefined
    at findTargetRendererHelper (/tracing/metrics/system_health/loading_metric.html:36:33)
    at timeToFirstContentfulPaintMetric (/tracing/metrics/system_health/loading_metric.html:230:26)
    at Object.loadingMetric (/tracing/metrics/system_health/loading_metric.html:425:5)
    at getNavigationTTIIntervals_ (/tracing/metrics/system_health/power_metric.html:55:19)
    at computeLoadingMetric_ (/tracing/metrics/system_health/power_metric.html:237:21)
    at new powerMetric (/tracing/metrics/system_health/power_metric.html:272:5)
    at runMetrics (/b/c/b/Mac_Retina_Perf__4_/src/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:37:14)
    at metricMapFunction (/b/c/b/Mac_Retina_Perf__4_/src/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:71:18)
    at Object.mapSingleTrace (/tracing/mre/map_single_trace.html:41:7)
    at eval (/b/c/b/Mac_Retina_Perf__4_/src/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:61:18)

Comment 1 by skyos...@chromium.org, Sep 29 2016

Owner: alexandermont@chromium.org
Status: Assigned (was: Untriaged)
First failing build:

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

I'm suspecting this patch from the catapult roll:

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+/ee7da6a366113b3ac7732ed78519589457f26911

alexandermont@, could you take a look? I'll disable the test in the meanwhile.

Comment 2 by sullivan@chromium.org, Sep 29 2016 

I think this is a dupe of  bug 650306 ?

Comment 3 by skyos...@chromium.org, Sep 29 2016

Mergedinto: 650306
Status: Duplicate (was: Assigned)
Indeed, sorry I missed it.
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 29 2016 

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

commit f1e10262a4bd54ea24fba0b63d74a5507023d69e
Author: skyostil <skyostil@chromium.org>
Date: Thu Sep 29 16:06:07 2016

Disable battor.power_cases_no_chrome_trace

This benchmark is currently red on mac.

BUG= 651384 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
TBR=alexclarke@chromium.org
NOTRY=true

Review-Url: https://codereview.chromium.org/2382473003
Cr-Commit-Position: refs/heads/master@{#421834}

[modify] https://crrev.com/f1e10262a4bd54ea24fba0b63d74a5507023d69e/tools/perf/benchmarks/battor.py
►

Sign in to add a comment