All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=705428

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyxQELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IpYBQ2hyb21pdW1QZXJmL2Nocm9taXVtLXJlbC1tYWMxMS1haXIvc3lzdGVtX2hlYWx0aC5jb21tb25fZGVza3RvcC90aW1lVG9GaXJzdE1lYW5pbmdmdWxQYWludF9hdmcvbG9uZ19ydW5uaW5nX3Rvb2xzL2xvbmdfcnVubmluZ190b29sc19nbWFpbC1mb3JlZ3JvdW5kDAsSDVN0b3BwYWdlQWxlcnQY84wbDA


Bot(s) for this bug's original alert(s):

chromium-rel-mac11-air

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983984268396407648

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983984245458974336

I mistakenly kicked off a bisect job of #c3 with a wrong configuration (not in return_code mode)
#c4 should run with a right configuration.

=== BISECT JOB RESULTS ===
NO Test failure found

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/long_running_tools/long_running_tools_gmail-foreground

Revision             Exit Code      N
chromium@444019      1 +- N/A       20      good
chromium@444066      1 +- N/A       20      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=long.running.tools.gmail.foreground system_health.common_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983984245458974336

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5310969418350592


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/long_running_tools/long_running_tools_gmail-foreground

Revision             Result                  N
chromium@444019      510.785 +- 109.739      13      good
chromium@444066      546.088 +- 103.725      8       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=long.running.tools.gmail.foreground system_health.common_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983984268396407648

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5282896438362112


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

charliea, could you take a look?

The test looks not reporting any data, but it looks running correctly regarding to the bisect report of #6.
(please ignore the result of #7. it ran with a wrong configuration)

Kicking this over to rnephew@, the current perfbot health sheriff.

It looks like this alert is for long_running:tools:gmail-foreground only. (Let me know if I am reading the alert wrong, but its what shows up when I click on the link). Since this test was disabled right after the last alert, I'm guessing this is not a real problem.

commit 33818797373a6eff577677cebd2f659a1328d053
Author: skyostil <skyostil@chromium.org>
Date:   Tue Jan 17 08:39:38 2017 -0800

    perf: Disable long_running:tools:gmail-foreground
    
    This benchmark is producing too much trace data, causing results
    processing to fail.
    
    BUG= 681839 
    
    Review-Url: https://codereview.chromium.org/2635983004
    Cr-Commit-Position: refs/heads/master@{#444069}

These graphs show data for long_running_tools_gmail-foreground stop, but the data for the other long_running_tools user stories continues to be collected.

https://chromeperf.appspot.com/report?sid=cb501285bbf20cfab815b104637801aa4d4fe29c859e2909a5e6ea604c3e44fe

Thanks for looking at this Randy!

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982624474049613088

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/long_running_tools/long_running_tools_gmail-foreground

Revision             Result                  N
chromium@444019      521.178 +- 148.643      14      good
chromium@444066      511.237 +- 159.448      13      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=long.running.tools.gmail.foreground system_health.common_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982624474049613088

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5282896438362112


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!