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

Issue 612204 link

Starred by 1 user
Status: Fixed
Owner:
█ pras...@chromium.org
Last visit 27 days ago
Closed: May 2016
Cc:
█ mikec...@chromium.org
█ yolandyan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Hook up the WebView perf bisect bot to the chromium.perf webview bots.

Project Member Reported by mikec...@chromium.org, May 16 2016 
Would like to setup the webview bisect bot to be the default bisect bot that is triggered thru the perf dashboard for the new chromium.perf WebView bots.

The bisect bot...
https://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_aosp_perf_bisect

The chromium perf bots....
https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf%20(1)
https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf%20(2)
https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf%20(3)

Not too sure how the bisect bots are setup, but we will also need the run_benchmark arg to be "--browser=android-webview" in the Bisect config file.

Comment 1 by pras...@chromium.org, May 16 2016

Status: Fixed (was: Untriaged)
Modified bot_browser_map and bisect_bot_map to reflect this changes.
Now the bisect jobs triggered for webview perf bots are directed to android_webview_aosp_perf_bisect bisect bot with "--browser=android-webview" in the benchmark.

https://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_aosp_perf_bisect/builds/144

Marking this as fixed, please feel free to re-open if you see any issue with bisect config.
►

Sign in to add a comment