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

Issue 889167 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ nednguyen@chromium.org
benjhayden@chromium.org
dtu@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Telemetry - Surface swarming info in histogramset

Project Member Reported by simonhatch@chromium.org, Sep 25 
dtu@ was investigating a no-repro case, boiled it down to a change in swarming bot between runs

On mobile runs, we have the device id embedded in the histogram data, but we don't bother for desktop since historically they all ran on the same machine. Should we surface the swarming bot id or something?

Comment 1 by dtu@chromium.org, Sep 25 

The alert in question was this one:
https://chromeperf.appspot.com/report?sid=c55ad6680124113714040cd05862c620687499c0a6628f716651c2a0511b7971&rev=592311

The metric history shows a bunch of similar invalid alerts. The Pinpoint results showed a strong bimodality, where the peaks correlated with device.

Comment 2 by simonhatch@chromium.org, Sep 27 

We could hook into run_performance_tests here: https://cs.chromium.org/chromium/src/testing/scripts/run_performance_tests.py?q=run_performance&sq=package:chromium&g=0&l=114 and pass a param into run_benchmark with additional diagnostics we want added with the histogram output?

Comment 3 by eakuefner@chromium.org, Nov 12

Cc: -eakuefner@chromium.org

Comment 4 by benhenry@google.com, Jan 16 (6 days ago)

Components: Test>Telemetry

Comment 5 by benhenry@google.com, Jan 16 (6 days ago)

Components: -Speed>Telemetry
►

Sign in to add a comment