History log of /external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
021ed349470fbaa3979898c2d8680ab67f7d35b3 21-Dec-2016 Ting-Yuan Huang <laszio@chromium.org> telemetry_AFDOGenerate: collect perf.data with images by clang

The code layout can be quite different by gcc and clang/llvm. To
make most of afdo, feedback file used by clang needs to be collected
on images built by llvm.

BUG=chromium:676173
TEST=Run and check files on gs

Change-Id: I0fc385b0f1914367ed2e9f4a24273e729ded3310
Reviewed-on: https://chromium-review.googlesource.com/422540
Commit-Ready: Ting-Yuan Huang <laszio@chromium.org>
Tested-by: Ting-Yuan Huang <laszio@chromium.org>
Reviewed-by: Yunlian Jiang <yunlian@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
0ab93253bcc62fe7a68698fd89448c20479f33b9 13-Oct-2016 Ting-Yuan Huang <laszio@chromium.org> telemetry_AFDOGenerate: Cutdown the training set.

This has been causing some builders to timeout.

BUG=chromium:653238
TEST=none

Change-Id: I3a433af99b12b105a461c57a0655eb433e7a7434
Reviewed-on: https://chromium-review.googlesource.com/398199
Commit-Ready: Ting-Yuan Huang <laszio@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
Tested-by: Ting-Yuan Huang <laszio@chromium.org>
Reviewed-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
89873ffc4ccce949b0a3953f6a039d45376ed758 02-Aug-2016 Ting-Yuan Huang <laszio@chromium.org> telemetry_AFDOGenerate: switch to page_cycler_v2.

The original page_cycler is deprecated and not available anymore.

BUG=none
TEST=test_that --board=$BOARD $DUT_ADDR \
--args=" run_local=[True|False] test=$TESTS " \
telemetry_AFDOGenerate

Change-Id: I1b69fc48d162030d8738059c213d6b8e7f78b9a5
Reviewed-on: https://chromium-review.googlesource.com/365190
Commit-Ready: Ting-Yuan Huang <laszio@chromium.org>
Tested-by: Ting-Yuan Huang <laszio@chromium.org>
Reviewed-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
da018df37ab513d1fe2e92ecf5d0b4ae841cd85e 21-Jul-2016 Luis Lozano <llozano@chromium.org> AFDO: Allow to run AFDO profile on samus, link

Need to move AFDO profile collection to a newer board. Because of a
restriction in autotest, this needs to be run on a machine with at least
2GB in /tmp. So, allow to run this on samus, link.

BUG=None
TEST=Will verify that there are no performance implications.

Change-Id: I3fbaa96f888f38d63e522e514a3c33663ad7561f
Reviewed-on: https://chromium-review.googlesource.com/362073
Commit-Ready: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
Reviewed-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
d118012af85d2717da7144cf95a07943b794e7c8 10-Apr-2016 Ting-Yuan Huang <laszio@chromium.org> Disable telemetry_on_dut in telemetry_AFDOGenerate.

The benchmarks act as a training set and scores are irrelevant.
Local telemetry scripts influence the perf based profiling results.

BUG=none
TEST=test_that --board=$BOARD $DUT \
--args="ignore_failures=True local=True \
gs_test_location=True" \
telemetry_AFDOGenerate

Change-Id: Ifcb2fd19c08894a68da72c3bb2de4ce9321310c2
Reviewed-on: https://chromium-review.googlesource.com/338047
Commit-Ready: Ting-Yuan Huang <laszio@chromium.org>
Tested-by: Ting-Yuan Huang <laszio@chromium.org>
Reviewed-by: Caroline Tice <cmtice@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
9162c55fe4568d1ef42d1f5e5f57484285038c14 09-Mar-2016 Luis Lozano <llozano@chromium.org> AFDO: reduce time for profile collection

Profile collection is taking longer since when this process was started.
This may cause timeout problems in the PFQ builder especially when
benchmarks are retried. This may also be the cause for a weird
linux "perf" failure where it runs out-of-memory at the end of the
profile collection. To ameliorate these problems, I am reducing
the number of iterations for the benchmark that takes the longest time.

BUG=chromium:593086
BUG=chromium:581488
TEST=executed by hand. verified time is reduced.

Change-Id: I70824d0ca47da6d77bd2018e4208681bb2a25fa7
Reviewed-on: https://chromium-review.googlesource.com/331833
Commit-Ready: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
Reviewed-by: Caroline Tice <cmtice@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
e97b5c96abaad985290993e57b7567bc8dbc76f5 26-Feb-2016 Luis Lozano <llozano@chromium.org> Temporarily remove smoothness.tought_webgl_cases.

This telemetry benchmark seems to be failing very
frequently. Remove until it is fixed. It has caused
increased times in AFDO collection and sometimes
timeouts for the lumpy-chrome-pfq builder.

BUG=chromium:590127
chromium:589905
TEST=none.

Change-Id: I91c03b14451f22b1425d9abea1cb003bf37cdb06
Reviewed-on: https://chromium-review.googlesource.com/329424
Reviewed-by: Luis Lozano <llozano@chromium.org>
Commit-Queue: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
6b2887a66f032115233cf0b45f7cc80a09ab0939 08-Oct-2015 Luis Lozano <llozano@chromium.org> AFDO: remove page_cycler.dhtml from training set.

This benchmark has been removed from Telemetry.

BUG=None
TEST=test_that telemetry_AFDOGenerate

Change-Id: If4caf3f5b14d740fcb23684afa0d6e1353cf50b3
Reviewed-on: https://chromium-review.googlesource.com/304800
Commit-Ready: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
a600d5519d7949ee9470e07aac86bed7343cfcba 09-Sep-2015 Luis Lozano <llozano@chromium.org> AFDO: Use Telemetry and Superhero to collect AFDO profile.

Until now we have been avoiding using Telemetry directly to
run the benchmarks used in the profile collection. Telemetry
is now much more stable on ChromeOS so we can give it a try.
I also updated the list of benchmars in the profile to base
it on the Superhero benchmarks. This brings more "diversity"
to the profile set.
Also, added logic to retry benchmarks in case of failure.

With these chanages we get upto 19% improvement on some
benchmarks.

BUG=None
TEST=Collected profile several times. Tested retry logic.

Change-Id: I138cadf904e40fcbc8b8d6936c65d887dd0bca5e
Reviewed-on: https://chromium-review.googlesource.com/298062
Commit-Ready: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
Reviewed-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
45b1d5ee093a1df18e286e1340c1b64145c18d4d 15-Sep-2014 Yunlian Jiang <yunlian@google.com> modify the comment of HOWTORUN for the test.

BUG=None
TEST=It shows the right commandline now.

Change-Id: If98f6e566c1e3af01fa512d182653cfcc38e5772
Reviewed-on: https://chromium-review.googlesource.com/218064
Reviewed-by: Luis Lozano <llozano@chromium.org>
Commit-Queue: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
09ef8f7eeda0452d48b53c4e28a1c6bdb24d0d7f 27-Aug-2014 Luis Lozano <llozano@chromium.org> Added some logging to GS uploads to diagnose some failures.

BUG=None
TEST=None

Change-Id: I667fe174891a5cd00034edb0168ebf5e3e94ed3e
Reviewed-on: https://chromium-review.googlesource.com/214363
Reviewed-by: Caroline Tice <cmtice@chromium.org>
Reviewed-by: Han Shen <shenhan@google.com>
Commit-Queue: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
d085cf6e4352c2cc62625ac3d161b1234b56e869 13-Aug-2014 Luis Lozano <llozano@chromium.org> List all the boards where this test can be run (sandybridge boards).

BUG=None.
TEST=Tested on lumpy, parrot.

Change-Id: I74c6caaa07ab69bf2eb1f671460601ec5a7b1a1a
Reviewed-on: https://chromium-review.googlesource.com/212291
Reviewed-by: Yunlian Jiang <yunlian@chromium.org>
Commit-Queue: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
c56792f43a0cb224ae0c5bbc121d0519f991773a 11-Feb-2014 Luis Lozano <llozano@chromium.org> Navigate a pre-defined set of URLs for Chrome profile collection.

The purpose of this test is to exercise chrome with a meaningful set
of pages while a profile of Chrome is captured. It also aims at using
the minimum set of functionality from Telemetry since Telemetry is not
very stable on ChromeOS at this point.

This test is designed to be called from the telemetry_AFDOGenerate
server test. The server test will start the "perf" profiling tool on
the DUT before starting this test. It will also capture the chrome
profile and upload it to Google Storage to be used for an optimized
build of Chrome.

BUG=None
TEST=Tested with test_that and in combination with telementry_AFDOGenerated
server test.

Change-Id: Ibe94cef3000289f93b01fb82c56b8bb00f7ba802
Reviewed-on: https://chromium-review.googlesource.com/185735
Reviewed-by: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
Commit-Queue: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
c955980a394d10dd9c34784b7d57549344c905c5 06-Feb-2014 Luis Lozano <llozano@chromium.org> Add support for profiling using minimal functionality from Telemetry.

Telemetry benchmarks are quite flaky at this point in ChromeOS. So we
are adding a new mode to this test to capture the Chrome profile using
the minimal support from Telemetry. For that we need to control Chrome
directly which needs to be done with a client test. The client test
will ask Chrome to display the benchmarks pages directly instead of
using Telemetry "page sets" and "measurements" support.

BUG=None
TEST=Tested through test_that using client test (work in progress).
Verified the profile is captured and only one instance of the
profiler is executed.

Change-Id: I4140aa41b6930281fff1b1013c9664b5747a9516
Reviewed-on: https://chromium-review.googlesource.com/185123
Reviewed-by: Luis Lozano <llozano@chromium.org>
Commit-Queue: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
40b7d0d8a5da83d695903bd49c8deaa4572d309f 18-Jan-2014 Luis Lozano <llozano@chromium.org> Add current chrome version to generated AFDO perf data

Add the chrome version of the name of the generated AFDO perf.data
file. Had to add necessary support in cros_host class and in the
process commonized some code with site_sysinfo.py

BUG=None
TEST=Tested through test_that.

Change-Id: I4d6537c78f21febadc566b7ea8b3238dc809e135
Reviewed-on: https://chromium-review.googlesource.com/183132
Reviewed-by: Luis Lozano <llozano@chromium.org>
Commit-Queue: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
63b761b31094fa342415614f5c5a31e8694885bd 16-Jan-2014 Luis Lozano <llozano@chromium.org> Reduced the list of tests to run to more stable ones

Do this for now so that testing of whole infrastructure is easier.

BUG=None
TEST=Tested locally through test_that.

Change-Id: Ied9cae3acabcc64450e64cc44bf65015bb2010ab
Reviewed-on: https://chromium-review.googlesource.com/182866
Reviewed-by: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
Commit-Queue: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py
23ae319340ac2ccacc1fcafe605daf4f9b2f9838 09-Nov-2013 Luis Lozano <llozano@chromium.org> Add AFDOGenerate test to generate AFDO profile data

This runs a pre-determined set of benchmarks on the
DUT under the monitoring of the "perf" linux tool and
copies the resulting data to Google Storage to be
used by the AFDO optimized build.

As part of this, modified the telemetry_runner code
to support running tests without a devserver.

BUG=None
TEST=Tested by hand using the --local flag.
Tested with my own instance of autotest.

Change-Id: Ia237b393ab0f37a1f6e56e857c4aa39474bf72a6
Reviewed-on: https://chromium-review.googlesource.com/176286
Reviewed-by: Luis Lozano <llozano@chromium.org>
Commit-Queue: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
/external/autotest/server/site_tests/telemetry_AFDOGenerate/telemetry_AFDOGenerate.py