| 60ddbb32d915f326965b6b03c7f701a5471d2503 |
|
23-May-2016 |
Keith Haddow <haddowk@chromium.org> |
[autotest] Update how the miletstone is discovered.
Use the test attribute CHROMEOS_RELEASE_CHROME_MILESTONE to determine
the milestone of the test results if it is available.
BUG=chromium:614075
TEST=ran unit tests localy
Change-Id: Ie63d35a4a8255326d623db5fd9578b8c2fe09dc4
Reviewed-on: https://chromium-review.googlesource.com/346722
Commit-Ready: Keith Haddow <haddowk@chromium.org>
Tested-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Rohit Makasana <rohitbm@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 52e6552197e7a92034587cf1527f532928ffd838 |
|
01-Apr-2016 |
Keith Haddow <haddowk@chromium.org> |
Fix devfault_rev flag to have pre-pended r_ and move to cros version.
BUG=chromium:599922
TEST=ran unit tests localy
Change-Id: I9c300fd9d0f512d16335cdbf4ab625b1de6c8d92
Reviewed-on: https://chromium-review.googlesource.com/336804
Commit-Ready: Keith Haddow <haddowk@chromium.org>
Tested-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 1e5c701acaaf4ae81e232636ce5602f67bb2afaa |
|
10-Mar-2016 |
Keith Haddow <haddowk@chromium.org> |
Update the lab autotest code to send chart-json format data to
the chromeperf dashboard.
BUG=chromium:589868
TEST=Tested client side and server side tests locally, and unit tests.
Change-Id: Ief821a2d524313ef6328bf3749760e4df906e630
Reviewed-on: https://chromium-review.googlesource.com/331795
Commit-Ready: Keith Haddow <haddowk@chromium.org>
Tested-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Keith Haddow <haddowk@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 7a5a7bd64357dd98917c47415359d4bc6067157b |
|
06-Feb-2016 |
Keith Haddow <haddowk@chromium.org> |
Add two new supplemental properties for chromeperf data.
a_jobname: uniquely identifies the job in the autotest system
so logs from the job run can be linked.
a_variant_name: the variant name so it can be retrieved without
parsing the platform name.
BUG=chromium:584053
TEST=Ran unit tests in local client, ran end to end test on local
Autotest instance.
Change-Id: Ifd09d29df73fa689bcfb355d74321fc45b44f0ee
Reviewed-on: https://chromium-review.googlesource.com/326471
Commit-Ready: Keith Haddow <haddowk@chromium.org>
Tested-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Matt Sheets <msheets@chromium.org>
Reviewed-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| b497616a0f537c1b84156b10a78760df0b400626 |
|
04-Feb-2016 |
Dan Shi <dshi@chromium.org> |
Revert "Add two new supplemental properties for chromeperf data."
This reverts commit bc455109c4fdb322fcc664dde699294aab26006c.
Change-Id: I2f096d2a0a16222aeefcab47d9beee9cb226c0c8
Reviewed-on: https://chromium-review.googlesource.com/326132
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| bc455109c4fdb322fcc664dde699294aab26006c |
|
03-Feb-2016 |
Keith Haddow <haddowk@chromium.org> |
Add two new supplemental properties for chromeperf data.
a_afe_job_id: uniquely identifies the job in the autotest system
so logs from the job run can be linked.
a_variant_name: the variant name so it can be retrieved without
parsing the platform name.
BUG=chromium:584053
TEST=Ran unit tests in local client.
Change-Id: I74ae7e57586fe34c1b0a27c34e0b3cd89881c752
Reviewed-on: https://chromium-review.googlesource.com/325544
Commit-Ready: Keith Haddow <haddowk@chromium.org>
Tested-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Matt Sheets <msheets@chromium.org>
Reviewed-by: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| b9fec886eece8c4992bf663580c2b88e259ffafb |
|
06-Jan-2016 |
Dan Shi <dshi@google.com> |
[autotest] Support shadow config for perf_uploader
This change adds the support of a local shadow config for perf_uploader. The
shadow config file should be in the same folder of perf_dashboard_config.json,
and named perf_dashboard_shadow_config.json.
BUG=None
TEST=local run, unittest
Change-Id: I1ff73b6dceabf3234c64ebdcbff665b2487906a3
Reviewed-on: https://chromium-review.googlesource.com/320395
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Fang Deng <fdeng@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 5a66aeacd84c09c862cc8bd9f372b549053eec26 |
|
14-Apr-2015 |
Quinten Yearsley <qyearsley@chromium.org> |
[autotest] Compute perf dashboard point IDs before sending.
Currently, this point ID is constructed on the perf dashboard side
when the data is received.
I believe that it's more ideal if the Chrome-OS-specific logic
is moved here:
- This will simplify the dashboard code and make it more consistent.
- This also means that if we want to send Chrome OS data with
different kinds of point IDs, that's also possible.
This also adds validation for the version numbers, so that when a
version number that doesn't match the expected format is used,
a clearer error message should be printed.
BUG=chromium:476188
TEST=Test case test_get_id_from_version and test_get_version_numbers added.
Change-Id: I193dc05d9621d08f1add2a4c0aebf63b01afc3b1
Reviewed-on: https://chromium-review.googlesource.com/265726
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Trybot-Ready: Quinten Yearsley <qyearsley@chromium.org>
Tested-by: Quinten Yearsley <qyearsley@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| ad38c6a1316c01524ce05c86cb65e0d873f4cc56 |
|
14-Apr-2015 |
Quinten Yearsley <qyearsley@chromium.org> |
[autotest] Minor style change.
BUG=None
TEST=None
Change-Id: I6f189a60ce66052909f48902ea96d2374f622928
Reviewed-on: https://chromium-review.googlesource.com/265557
Reviewed-by: Fang Deng <fdeng@chromium.org>
Tested-by: Quinten Yearsley <qyearsley@chromium.org>
Trybot-Ready: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| eb04ae43956d2be5cf4c247dc4858dc656c4d29d |
|
05-Feb-2015 |
Kris Rambish <krisr@chromium.org> |
Add variant handling to performance tests.
BUG=chromium:454915
TEST=Unit test for perf_uploader, ran network_WiFi_Perf
Change-Id: I9718b340fced30756d6b7f015e3a7945b1aa4f45
Reviewed-on: https://chromium-review.googlesource.com/246310
Tested-by: Kris Rambish <krisr@chromium.org>
Reviewed-by: Bindu Mahadev <bmahadev@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Kris Rambish <krisr@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 390e85c4dbadd11d19f5c61665847e6db4d931aa |
|
09-Jan-2015 |
“Keith <haddowk@google.com> |
Add the test hostname to performance test results.
BUG=chromium:447402
TEST=Ran unit test in local client.
Change-Id: I761208affe9fb4cd710f6d45817e013b06a845c8
Reviewed-on: https://chromium-review.googlesource.com/239980
Commit-Queue: Keith Haddow <haddowk@chromium.org>
Trybot-Ready: Keith Haddow <haddowk@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
Tested-by: Keith Haddow <haddowk@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| ac0b164644b3be0d851da77612a222572b81de21 |
|
20-Nov-2014 |
Keith Haddow <haddowk@chromium.org> |
Add hardware id to the supplimental data that is sent to the chromeperf dashboard.
BUG=chromium:435245
TEST=Ran unit tests in local client, ran tko/parse.py in local autotest
enviroment.
Change-Id: I64fd4cda5b4ac9cac24df82420b5b231d5f7bc3e
Reviewed-on: https://chromium-review.googlesource.com/231101
Reviewed-by: Keith Haddow <haddowk@chromium.org>
Commit-Queue: Keith Haddow <haddowk@chromium.org>
Tested-by: Keith Haddow <haddowk@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 890cab3dfab750585076907f03a7442b7cb681a4 |
|
21-Nov-2014 |
Ilja Friedel <ihf@chromium.org> |
Revert "autotest: do not upload perf data from branches."
This reverts commit 4aee1484a2e27582b050dbfaa616601a2b54225c.
The test team needs data from branches for now, even if the graphs are bad.
BUG=chromium:365051,chromium:342552
Change-Id: I49f88cca10db345874a876b3853c7dfeb4b6292f
Reviewed-on: https://chromium-review.googlesource.com/231171
Reviewed-by: Ilja Friedel <ihf@chromium.org>
Tested-by: Ilja Friedel <ihf@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 4aee1484a2e27582b050dbfaa616601a2b54225c |
|
14-Nov-2014 |
Ilja H. Friedel <ihf@chromium.org> |
autotest: do not upload perf data from branches.
This easily confuses perf dashboard users.
Also update the samples in the unittest to mirror current versions.
BUG=chromium:365051,chromium:342552
TEST=perf_uploader_unittest.py
Change-Id: I585e829f56c41d2733bfa9b41fc1e871f7b4bbc9
Reviewed-on: https://chromium-review.googlesource.com/229750
Reviewed-by: Fang Deng <fdeng@chromium.org>
Tested-by: Ilja Friedel <ihf@chromium.org>
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Ilja Friedel <ihf@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 1568334ca72a3ee8585cca5b8646059e3da4747b |
|
14-Nov-2014 |
cmtice <cmtice@google.com> |
Fix unittest problem uncovered with GCC 4.9
When building 64-bit boards using GCC 4.9, we uncovered a unittest
problem where the unittest was incorrectly depending on python
dictionary entries always being in the same order (dictionaries are
supposed to be unordered).
This CL fixes the bug.
BUG=chromium:430296
TEST=Tested this fix both with GCC 4.9 build, when test failed without the
fix; and with GCC 4.8 build, to verify GCC 4.8 build continues to work
with this fix.
Change-Id: I083a2c9eb6b2ba21179d3227378805c3591c0c33
Reviewed-on: https://chromium-review.googlesource.com/229752
Reviewed-by: Luis Lozano <llozano@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Caroline Tice <cmtice@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| ad2c1e6dcda0294b24b8f447ed99f1fee995630c |
|
11-Jun-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
perf_uploader: Don't aggregate perf value with different graph
When we call output_perf_value with same description but different
graph name perf_uploader aggregate the value together so that when
we see result in dashboard we will only see average of every data
in the first graph only. This CL fixes that behavior by also looking
at graph name before aggregate perf data.
BUG=chromium:383164
TEST=Modify perf_uploader_unitest.py for new behavior and Run it.
Change-Id: Ic543dcf3c57be995a89f553891b5de91a931ca86
Reviewed-on: https://chromium-review.googlesource.com/203331
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org>
Tested-by: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| fd03bcb0d4ae39be1d10d82d7d937266771360cd |
|
17-May-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
perf_uploader: send 'higher_is_better' info to dashboard
Currently perf dashboard guess higher or lower is better based
on unit associated with perf value. This CL send the info to
the dashboard to remove guesswork by adding this info to the
json that will be uploaded to the server.
BUG=chromium:280649
TEST=Add higher_is_better to expected json output in unittest
then run perf_uploader_unittest.py. Unittest passed.
Change-Id: Ic5a3e095ab2152682e025a8c80e52b6131aeb14d
Reviewed-on: https://chromium-review.googlesource.com/200330
Reviewed-by: Quinten Yearsley <qyearsley@google.com>
Commit-Queue: Quinten Yearsley <qyearsley@google.com>
Tested-by: Quinten Yearsley <qyearsley@google.com>
Reviewed-by: Fang Deng <fdeng@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 947502ebf6f02d7b4c7e7434001dde2a1a416d16 |
|
07-May-2014 |
Fang Deng <fdeng@chromium.org> |
[autotest] Perf tests must speicify config data.
Perviously, the specification of config data is not enforced
by code. When missing, default config data will be used. This
causes inconsistency when people lands their test first and the
change to perf_dashboard_config is pushed to prod later.
This cl fixes this problem by enforcing the specification
of config data for all perf tests. If the config data is
missing, perf data will not be uploaded.
BUG=chromium:371022
TEST=Test locally by removing entry of power_Resume from
perf_dashboard_config. Confirmed data will not be uploaded.
unittests.
Change-Id: Icaa1e854c33a617218d87b6c496894a8cf178382
Reviewed-on: https://chromium-review.googlesource.com/198747
Tested-by: Fang Deng <fdeng@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| 7f24f0bfe69b2f36ba74350fba9ad547ac55571c |
|
12-Nov-2013 |
Fang Deng <fdeng@chromium.org> |
[autotest] test can output graph name when calling output_perf_value
Previously, if we want to group several perf measurements together
to be displayed on the same graph, we need to specify the mapping
information in perf_dashbaord_config.json. However, some tests
like telemetry_Benchmarks output many metrics. We would end up
with a very huge config file if we specify them all. It would require
much efforts if those metrics change in the future.
This change is to allow test to output graph names dynamically.
1) output_perf_value now takes a new arg 'graph'. This value is
written to the json file perf_measurements.
2) a new column 'graph' is added to the database table
tko_iteration_perf_value.
3) the tko parser is modified to store the value of 'graph' from
perf_measurements to the database.
4) perf_uploader is modified to upload a perf measurement to the
specific graph if 'graph' is set.
Example:
Previously, if we wanted to specify group "metric1" and "metric2"
to the same graph "metricGroupA", and group "metric3" and "metric4"
to "metricGroupB", the json needed to look like:
{
“autotest_name”: “myTest”,
“master_name”: “myMaster”,
“dashboard_test_name”: “myCoolTest”
“graphs”: [
{
“graph_name”: “metricGroupA”,
“descriptions”: [“metric1”, “metric2”]
},
{
“graph_name”: “metricGroupB”,
“descriptions”: [“metric3”, “metric4”]
},
]
}
After this change list lands, the json file will not
take "graphs" configuration. It will look like.
{
“autotest_name”: “myTest”,
“master_name”: “myMaster”,
“dashboard_test_name”: “myCoolTest”
}
Meanwhile, the test should call
output_perf_value(description="metric1", units=.., higher_is_better=..,
graph='metricGroupA')
output_perf_value(description="metric2", units=.., higher_is_better=..,
graph='metricGroupA')
output_perf_value(description="metric3", units=.., higher_is_better=..,
graph='metricGroupB')
output_perf_value(description="metric4", units=.., higher_is_better=..,
graph='metricGroupB')
BUG=chromium:315274
TEST=1) Verified all unit tests passed: version_1_unittest.py,
perf_uploader_unittest.py
2) Modify perf_uploader.py to use staging perf dashboard server
_DASHBOARD_UPLOAD_URL =
'https://chrome-perf.googleplex.com/add_point'
Modify platform_BootPerfServer to output graph name.
Invoked platform_BootPerfServer from local AFE.
Verify that the perf_measurements file have the graph name.
Verify that the data was displayed correctly in the dashboard.
3) python migrate.py sync 82, to verify column 'graph' get created
python migrate.py sync 81, to verify column 'graph' is dropped
DEPLOY=migrate (/usr/local/autotest/database$ python migrate.py sync 82)
Change-Id: I0b746f4ab3162eb7ba4aefa12294b7a60e326513
Reviewed-on: https://chromium-review.googlesource.com/176575
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
Tested-by: Fang Deng <fdeng@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|
| f9bef6c3bf7252e565622ade3f4680282f150ca0 |
|
05-Aug-2013 |
Dennis Jeffrey <dennisjeffrey@chromium.org> |
Autotest TKO parser now sends measured perf data to chrome's performance dashboard.
Any performance autotests that invoke self.output_perf_value() will now
have those outputted results uploaded to chrome's performance dashboard,
as part of the autotest TKO parsing stage. For now, a message is logged
to the .parse.log output file indicating success or failure of the
upload. In the future, failed uploads will need to be retried, and
better insight will need to be provided as to how well the perf_uploader
module is performing.
BUG=chromium:258232
TEST=Invoked platform_GesturesRegressionTest using a local instance of
the autotest frontend, and a local instance of Chrome team's perf
dashboard. Then verified that the perf data outputted by the test appeared
on the perf dashboard. Also verified that perf_uploader_unittest.py passes.
Change-Id: Id685deda129056465350a5be8effc9aa97fa9bb4
Reviewed-on: https://gerrit.chromium.org/gerrit/64672
Commit-Queue: Dennis Jeffrey <dennisjeffrey@chromium.org>
Reviewed-by: Dennis Jeffrey <dennisjeffrey@chromium.org>
Tested-by: Dennis Jeffrey <dennisjeffrey@chromium.org>
/external/autotest/tko/perf_upload/perf_uploader_unittest.py
|