[meta] Improve benchmarking and UMA recording for startup latency on Android |
||||||||||||||
Issue description
Showing comments 125 - 224
of 224
Older ›
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fcfe9a6f17f02771890c03d666dcebf560eca909 commit fcfe9a6f17f02771890c03d666dcebf560eca909 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Mon Sep 03 17:03:24 2018 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) https://chromium.googlesource.com/catapult.git/+log/713e916190aa..88dc49aaadb0 git log 713e916190aa..88dc49aaadb0 --date=short --no-merges --format='%ad %ae %s' 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2018-09-03 anthonyalridge@google.com Include testing of significant impacts on a per story basis. 2018-09-03 wangge@google.com Add M70 branch number. Created with: gclient setdep -r src/third_party/catapult@88dc49aaadb0 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498,chromium:383566,chromium:866423, chromium:863390 TBR=sullivan@chromium.org Change-Id: I3249938bc929dcbccb370351dd528c59afe2cccd Reviewed-on: https://chromium-review.googlesource.com/1202504 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#588413} [modify] https://crrev.com/fcfe9a6f17f02771890c03d666dcebf560eca909/DEPS
,
Sep 4
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/79290c7a2366a332f608c8502cb69e727b7278bc commit 79290c7a2366a332f608c8502cb69e727b7278bc Author: Egor Pasko <pasko@chromium.org> Date: Mon Sep 03 18:12:12 2018 benchmarks: Graduate startup.mobile from experimental Recently the start_with_url.{cold,warm}.startup_pages became flaky and were disabled. The unfortunate consequence is that the corresponding dashboard graphs are going silent. The experimental.mobile.startup benchmark has already bare minimum functionality to start running on bots (WPR support, meaningful results for cold startup with intent). Some data is better than no data at all. Rename 'experimental.startup.mobile' to 'startup.mobile'. Enabling the runs on bots will be done separately. Bug: 760498 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Ia6ffb71a4b20d8969c5bef9febd3c5d8e04a82ff Reviewed-on: https://chromium-review.googlesource.com/1202665 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588421} [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/bot_platforms.py [modify] https://crrev.com/79290c7a2366a332f608c8502cb69e727b7278bc/tools/perf/core/test_data/benchmarks_to_shard.json
,
Sep 5
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4dbfe75699880b24883d791cbfd926df4d62ac66 commit 4dbfe75699880b24883d791cbfd926df4d62ac66 Author: Egor Pasko <pasko@chromium.org> Date: Wed Sep 05 11:22:19 2018 benchmarks: Add a warm story to startup.mobile For the warm story we avoid flushing caches. Metrics will need more polishing for properly omitting the first result. This should be done for the cold benchmark as well, hence we'd still have a good separation between the benchmark driver and the metrics. Bug: 760498 Change-Id: Ie061852bd1c8893f5ea57b67c85a383bedf26a7c Reviewed-on: https://chromium-review.googlesource.com/1203936 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#588829} [modify] https://crrev.com/4dbfe75699880b24883d791cbfd926df4d62ac66/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/4dbfe75699880b24883d791cbfd926df4d62ac66/tools/perf/page_sets/data/startup_pages.json
,
Sep 6
,
Sep 9
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4a8318cdb33034a3510f875dc40214e892c1bb33 commit 4a8318cdb33034a3510f875dc40214e892c1bb33 Author: Ned Nguyen <nednguyen@google.com> Date: Sun Sep 09 09:52:34 2018 Update supported platforms of startup.mobile to only support mobile Note: the old Telemetry decorators no longer work on benchmarks TBR=pasko@chromium.org NOTRY=true # flake Bug: 760498 Change-Id: I514ebefb488db9934adcdde77c2f307a571183d6 Reviewed-on: https://chromium-review.googlesource.com/1215244 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#589797} [modify] https://crrev.com/4a8318cdb33034a3510f875dc40214e892c1bb33/tools/perf/benchmarks/startup_mobile.py
,
Sep 12
,
Sep 12
,
Sep 12
,
Sep 12
,
Sep 12
,
Sep 18
,
Sep 19
,
Sep 25
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/57806536bf88ef8ab0efd7d5e0930fc372407d0f commit 57806536bf88ef8ab0efd7d5e0930fc372407d0f Author: Ned Nguyen <nednguyen@google.com> Date: Tue Sep 25 09:44:38 2018 Remove legacy Android startup benchmarks This also removes the experimental tbmv2 startup benchmark: experimental.startup.android.coldish Bug: 760498 Change-Id: I8f5f7f6353cde2eca23e1e96fa67114bd1004816 Reviewed-on: https://chromium-review.googlesource.com/1242923 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org> Reviewed-by: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#593880} [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/benchmark.csv [delete] https://crrev.com/a184908f7b4ce3542fbabb332d5b1774d956fba2/tools/perf/benchmarks/start_with_url.py [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/android-nexus5x-perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/android_nexus5_perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/android_nexus5x_webview_perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/android_nexus6_webview_perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/linux-perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/mac-10_12_laptop_low_end-perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/mac-10_13_laptop_high_end-perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/win-10-perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/win_7_nvidia_gpu_perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/shard_maps/win_7_perf_map.json [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/core/undocumented_benchmarks.py [modify] https://crrev.com/57806536bf88ef8ab0efd7d5e0930fc372407d0f/tools/perf/expectations.config
,
Sep 25
The following revision refers to this bug: https://chromium.googlesource.com/catapult/+/2fa501d5727025a06b2658171cf14ea48275eafc commit 2fa501d5727025a06b2658171cf14ea48275eafc Author: Nghia Nguyen <nednguyen@google.com> Date: Tue Sep 25 10:06:44 2018 Remove legacy startup TBMv1 metrics This is blocked on https://chromium-review.googlesource.com/c/chromium/src/+/1242923 Bug: chromium:760498 Change-Id: I915e694fbf7baa25bc2caf05deb4d82c15c70b4e Reviewed-on: https://chromium-review.googlesource.com/1242924 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org> Reviewed-by: Egor Pasko <pasko@chromium.org> [delete] https://crrev.com/7931f7f4ae38599eae772a48208c0c6a3a292bbe/telemetry/telemetry/web_perf/metrics/startup.py [delete] https://crrev.com/7931f7f4ae38599eae772a48208c0c6a3a292bbe/telemetry/telemetry/web_perf/metrics/startup_unittest.py
,
Sep 25
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/52982fc80084dc8b2108b8f6235e088c8c34c95c commit 52982fc80084dc8b2108b8f6235e088c8c34c95c Author: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Date: Tue Sep 25 12:18:30 2018 Roll src/third_party/catapult 7931f7f4ae38..e5495aef8e46 (2 commits) https://chromium.googlesource.com/catapult.git/+log/7931f7f4ae38..e5495aef8e46 git log 7931f7f4ae38..e5495aef8e46 --date=short --no-merges --format='%ad %ae %s' 2018-09-25 ulan@chromium.org Add v8.console to the default categories. 2018-09-25 nednguyen@google.com Remove legacy startup TBMv1 metrics Created with: gclient setdep -r src/third_party/catapult@e5495aef8e46 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:880432,chromium:760498 TBR=sullivan@chromium.org Change-Id: Iafe7bf75a6b75abba5885eef2aafbc9e207cba6b Reviewed-on: https://chromium-review.googlesource.com/1242326 Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#593898} [modify] https://crrev.com/52982fc80084dc8b2108b8f6235e088c8c34c95c/DEPS
,
Sep 25
,
Oct 5
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/38715b2a0d263f460da4947ab0ffee6bff8c7bc4 commit 38715b2a0d263f460da4947ab0ffee6bff8c7bc4 Author: Ned Nguyen <nednguyen@google.com> Date: Fri Oct 05 22:46:05 2018 Remove experimental.startup.android.coldish benchmark scheduling code BUG:760498 This also reshard android_nexus5x_fyi_4_shard_map.json which may cause shifting data of heap_profiling.mobile.disabled benchmark TBR=pasko@chromium.org Change-Id: I561d9fbd628b2f53f6e043b524b93c32b03c56d1 Reviewed-on: https://chromium-review.googlesource.com/c/1265129 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#597353} [modify] https://crrev.com/38715b2a0d263f460da4947ab0ffee6bff8c7bc4/docs/speed/benchmark/benchmark_short_list.md [modify] https://crrev.com/38715b2a0d263f460da4947ab0ffee6bff8c7bc4/tools/perf/core/bot_platforms.py [modify] https://crrev.com/38715b2a0d263f460da4947ab0ffee6bff8c7bc4/tools/perf/core/perf_data_generator.py [modify] https://crrev.com/38715b2a0d263f460da4947ab0ffee6bff8c7bc4/tools/perf/core/shard_maps/android_nexus5x_fyi_4_shard_map.json
,
Oct 25
,
Nov 9
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f66562084955f8c351a4aacb8dec612aec012301 commit f66562084955f8c351a4aacb8dec612aec012301 Author: Egor Pasko <pasko@chromium.org> Date: Fri Nov 09 20:27:27 2018 startup benchmarks: remove legacy TBMv1 pagesets Remove the pagesets that were used for TBMv1 startup benchmarks. These benchmarks were removed already leaving the pagesets unused. We still depend on the json and the WPR archives in the TBMv2 benchmark (startup.mobile). Bug: 760498 Change-Id: I814840fd5696d8f7f696b29678c98ab4f0541b8b Reviewed-on: https://chromium-review.googlesource.com/c/1329662 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#606952} [delete] https://crrev.com/6e844c42a37cbe452e55f77acbe662892a44ad21/tools/perf/page_sets/startup_pages.py
,
Nov 13
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/45907441cc5d713e40b10ced13979481715629b4 commit 45907441cc5d713e40b10ced13979481715629b4 Author: Jean-denis Muys <jdmuys@chromium.org> Date: Tue Nov 13 15:24:46 2018 Added a Chrome Custom Tab start up benchmark to startup.mobile benchmark The new story is named cct:no_warmup:bbc Bug: 760498 Change-Id: I11a1d2e0b9b4a9dbfb4c4f31f039c4ca3bbe75c6 Reviewed-on: https://chromium-review.googlesource.com/c/1301914 Commit-Queue: Jean-Denis Muys <jdmuys@chromium.org> Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org> Reviewed-by: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#607592} [modify] https://crrev.com/45907441cc5d713e40b10ced13979481715629b4/tools/perf/benchmarks/startup_mobile.py [modify] https://crrev.com/45907441cc5d713e40b10ced13979481715629b4/tools/perf/expectations.config [modify] https://crrev.com/45907441cc5d713e40b10ced13979481715629b4/tools/perf/page_sets/data/startup_pages.json
,
Nov 20
,
Nov 20
,
Dec 6
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/10160cf2140000
,
Dec 6
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/10160cf2140000
,
Dec 10
The following revision refers to this bug: https://chromium.googlesource.com/catapult/+/60a61e85fed1aa7856f9dda3fe3983b6634404ad commit 60a61e85fed1aa7856f9dda3fe3983b6634404ad Author: Egor Pasko <pasko@chromium.org> Date: Mon Dec 10 16:04:11 2018 Add telemetry.core.util.FindLatestApkOnHost() In order to install MapsWebApk.apk in http://crrev.com/c/1352315 add an API to install APKs from "$CHROMIUM_OUTPUT_DIR/apks". Initially I thought it could be made during browser_finder.FindBrowser() by extending the |finder_options|, but it did not work because the platform was not initialized at that point. Since --chrome-root needs to be respected, the shared state will pull it from |finder_options| and push down to FindLatestApkOnHost(). To avoid duplication the android_browser_backend_settings is using the same function. Bug: chromium:760498 Change-Id: Ide5e54a21ffad2dcdcf41eb99ab458014cef5e5c Reviewed-on: https://chromium-review.googlesource.com/c/1363771 Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org> Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Ned Nguyen <nednguyen@google.com> [modify] https://crrev.com/60a61e85fed1aa7856f9dda3fe3983b6634404ad/telemetry/telemetry/core/util.py [modify] https://crrev.com/60a61e85fed1aa7856f9dda3fe3983b6634404ad/telemetry/telemetry/internal/backends/android_browser_backend_settings.py
,
Dec 10
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3c30b98acf5b782c34a3c048f3dfeaeb79f21351 commit 3c30b98acf5b782c34a3c048f3dfeaeb79f21351 Author: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Date: Mon Dec 10 20:07:53 2018 Roll src/third_party/catapult e09a3df387b3..60a61e85fed1 (1 commits) https://chromium.googlesource.com/catapult.git/+log/e09a3df387b3..60a61e85fed1 git log e09a3df387b3..60a61e85fed1 --date=short --no-merges --format='%ad %ae %s' 2018-12-10 pasko@chromium.org Add telemetry.core.util.FindLatestApkOnHost() Created with: gclient setdep -r src/third_party/catapult@60a61e85fed1 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498 TBR=sullivan@chromium.org Change-Id: Ic0d5dede30002cace3cf2b0facad86002d7f9d5a Reviewed-on: https://chromium-review.googlesource.com/c/1369837 Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#615217} [modify] https://crrev.com/3c30b98acf5b782c34a3c048f3dfeaeb79f21351/DEPS
,
Dec 11
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/143cd53c140000
,
Dec 11
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/143cd53c140000
,
Dec 14
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/120a5e2e140000
,
Dec 14
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/120a5e2e140000
,
Dec 17
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1152bd0e140000
,
Dec 17
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/1152bd0e140000
,
Dec 28
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14eb5e40940000
,
Dec 28
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/14eb5e40940000
,
Dec 28
The following revision refers to this bug: https://chromium.googlesource.com/catapult/+/ecf56e8e03cd13d93319c53330ea950f7ae7e51d commit ecf56e8e03cd13d93319c53330ea950f7ae7e51d Author: Egor Pasko <pasko@chromium.org> Date: Fri Dec 28 20:24:27 2018 Android: pull more lines from logcat by default I am try-running http://crrev.com/c/1352315 via Pinpoint using the bot android-go-perf. Example job: https://pinpoint-dot-chromeperf.appspot.com/job/14eb5e40940000 Individual tasks reveal in the logs that browser crashes appeared, like this: - android:id/alertTitle['Clankium has stopped'] The fragment of the logcat that Telemetry attaches does not contain the information about the crash, which complicates the investigation a lot. (!) The reason for the crash to be missing: only 500 lines are being pulled by Telemetry (running command "logcat -d -t 500") which covers about 30 seconds of idle time. During these last 30 seconds Telemetry had been waiting for devtools connection, and the crash causing he connection to be refused happened 40-50 seconds earlier. Increasing the limit from roughly 30 seconds to 90 seconds should give enough room. This translates to 3x the number of lines -> 1500. There are probably greener ways to do it, but I'd prefer this one character fix in the short term to unblock the investigation. Bug: chromium:760498 Change-Id: Ifd423c650082fe0f886d6c211520f0a48eaa0121 Reviewed-on: https://chromium-review.googlesource.com/c/1390663 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Egor Pasko <pasko@chromium.org> [modify] https://crrev.com/ecf56e8e03cd13d93319c53330ea950f7ae7e51d/telemetry/telemetry/internal/platform/android_platform_backend.py
,
Dec 28
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/cab6480a60dd6548037b12413ef98126d7424c8b commit cab6480a60dd6548037b12413ef98126d7424c8b Author: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Date: Fri Dec 28 21:19:22 2018 Roll src/third_party/catapult d1cc7e545a4c..ecf56e8e03cd (1 commits) https://chromium.googlesource.com/catapult.git/+log/d1cc7e545a4c..ecf56e8e03cd git log d1cc7e545a4c..ecf56e8e03cd --date=short --no-merges --format='%ad %ae %s' 2018-12-28 pasko@chromium.org Android: pull more lines from logcat by default Created with: gclient setdep -r src/third_party/catapult@ecf56e8e03cd The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:760498 TBR=sullivan@chromium.org Change-Id: I5219b29943983404fc5ee50fef0696feb7c1667b Reviewed-on: https://chromium-review.googlesource.com/c/1392289 Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#619193} [modify] https://crrev.com/cab6480a60dd6548037b12413ef98126d7424c8b/DEPS
,
Jan 4
Showing comments 125 - 224
of 224
Older ›
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
