Once this change lands: https://chromium-review.googlesource.com/c/chromium/src/+/1188777
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ad3eaa784018e9c780e3a2eda84cb6d49173a83f commit ad3eaa784018e9c780e3a2eda84cb6d49173a83f Author: Dominic Mazzoni <dmazzoni@chromium.org> Date: Wed Aug 29 18:24:12 2018 Add blink_perf accessibility test for large textareas. Bug: 875344 , 877669 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: I15bbd8c9f64d999f0d987af9d0b8d2b2785165be Reviewed-on: https://chromium-review.googlesource.com/1188777 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#587201} [modify] https://crrev.com/ad3eaa784018e9c780e3a2eda84cb6d49173a83f/docs/speed/benchmark/benchmark_ownership.md [add] https://crrev.com/ad3eaa784018e9c780e3a2eda84cb6d49173a83f/third_party/blink/perf_tests/accessibility/textarea-append.html [modify] https://crrev.com/ad3eaa784018e9c780e3a2eda84cb6d49173a83f/tools/perf/benchmarks/blink_perf.py [modify] https://crrev.com/ad3eaa784018e9c780e3a2eda84cb6d49173a83f/tools/perf/core/perf_data_generator.py
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6818ca8f1d19ebe081353799e91a8de365c89075 commit 6818ca8f1d19ebe081353799e91a8de365c89075 Author: Ned Nguyen <nednguyen@google.com> Date: Sat Sep 01 09:54:04 2018 Reshard perf benchmarks to include blink_perf.accessibility benchmark ** PERF SHERIFFS: this CL will cause regressions on many bots that are non bisectable ** Run: ./tools/perf/generate_perf_sharding ./tools/perf/generate_perf_data Bug: 877669 , 877643 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ifcd60511ce3647616672056d7f46e9ac53b00c54 Reviewed-on: https://chromium-review.googlesource.com/1199934 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#588278} [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/benchmark.csv [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/bot_platforms.py [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/perf_data_generator.py [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/android_go_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/android_nexus5_16_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/android_nexus5x_16_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/android_nexus5x_webview_16_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/android_nexus6_webview_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/linux_perf_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/mac_1012_low_end_26_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/mac_1013_high_end_26_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/win10_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/win7_nvidia_shard_map.json [modify] https://crrev.com/6818ca8f1d19ebe081353799e91a8de365c89075/tools/perf/core/shard_maps/win7_shard_map.json
This benchmark is now running: https://chromeperf.appspot.com/report dmazzoni@: you may want to file a bug against perf dashboard team (Component: "Speed>Dashboard") to set monitoring for this benchmark
Comment 1 by nednguyen@chromium.org
, Aug 26