what happened to page_cycler.typical_25?

[Luis Lozano]

telemetry was broken for a few days in ChromeOS and now I am seeing the following error:

what happened to page_cycler.typical_25?

was it renamed to page_cycler_v2.typical_25? and, if so, what is the difference?

Thanks

Luis

05/26 03:13:45.252 DEBUG|        base_utils:0176| Running 'ssh 100.107.160.7 python /home/chromeos-test/images/lumpy-chrome-pfq/R53-8372.0.0-rc3/telemetry_src/src/tools/perf/run_benchmark --verbose --browser=cros-chrome --output-format=chartjson --output-dir=/home/chromeos-test/images/lumpy-chrome-pfq/R53-8372.0.0-rc3/telemetry_src/src --remote=chromeos2-row3-rack9-host9 --pageset-repeat=1 page_cycler.typical_25'

05/26 03:14:03.834 DEBUG|  telemetry_runner:0284| Error occurred executing.

05/26 03:14:03.834 DEBUG|  telemetry_runner:0290| Completed with exit code: 255.

stdout:

stderr:Warning: Permanently added '100.107.160.7' (ECDSA) to the list of known hosts.

No benchmark named "page_cycler.typical_25".

Do you mean any of those benchmarks below?

Available benchmarks are:

  page_cycler.basic_oopif                 A benchmark measuring performance of the out-of-process iframes page

  page_cycler.intl_ar_fa_he              Page load time for a variety of pages in Arabic, Farsi and Hebrew.

  page_cycler.intl_es_fr_pt-BR           Page load time for a pages in Spanish, French and Brazilian Portuguese.

  page_cycler.intl_hi_ru                 Page load time benchmark for a variety of pages in Hindi and Russian.

  page_cycler.intl_ja_zh                 Page load time benchmark for a variety of pages in Japanese and Chinese.

  page_cycler.intl_ko_th_vi              Page load time for a variety of pages in Korean, Thai and Vietnamese.

  page_cycler.top_10_mobile              Page load time benchmark for the top 10 mobile web pages.

  page_cycler.tough_layout_cases         Page loading for the slowest layouts observed in the Alexa top 1 million.

  page_cycler_site_isolation.basic_oopif  A benchmark measuring performance of out-of-process iframes. 

  page_cycler_v2.typical_25              Page load time benchmark for a 25 typical web pages.

--

Luis A. Lozano |

Software Engineer |

llo...@google.com |

+1 (408)431-5164

[Luis Lozano]

+chromeos-toolchain and crosbolt interested parties

[Ned]

+Kouhei Ueno is working on PageCycler v2 

--
You received this message because you are subscribed to the Google Groups "telemetry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to telemetry+...@chromium.org.

[Luis Lozano]

I am pretty sure there are many reasons to have a Page Cycler v2 but can I ease into it?

Ie: please just don't remove page_cycler.typical_25 without giving us time to learn what v2 is and what changes we need to make as users of it.

[Luis Lozano]

it seems Kouhei is on vacation until may 30.

can you please restore page_cycler.typical_25 ASAP and until the point where we can migrate out of it? 

THanks

Luis

[Ned]

I just run tools/perf/run_benchmark --browser=system page_cycler.typical_25 I saw the same message that says No benchmark named page_cycler.typical_25. I think this is a serious bug in telemetry: https://bugs.chromium.org/p/chromium/issues/detail?id=615134

I will work on this.

On Thu, May 26, 2016 at 11:19 AM Ned <nedn...@google.com> wrote:

I am not sure what you mean. page_cycler.typical_25 is still in https://code.google.com/p/chromium/codesearch#chromium/src/tools/perf/benchmarks/page_cycler.py&l=166

[Ned]

I am not sure what you mean. page_cycler.typical_25 is still in https://code.google.com/p/chromium/codesearch#chromium/src/tools/perf/benchmarks/page_cycler.py&l=166

On Thu, May 26, 2016 at 11:17 AM Luis Lozano <llo...@google.com> wrote:

[Luis Lozano]

thanks!