| debda710223e62d448f2f39d378e5fe92144b1d4 |
|
08-Jul-2013 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: print raw metrics values in pickled logs
For development purpose, it is handy to be able to print the
raw metrics values in pickled logs.
BUG=chromium:235753
TEST=Run the command on a chromebook machine.
$ cd /usr/local/autotest/tests/firmware_TouchMTB
$ python tools/print_log.py tests/logs/lumpy/20130506_030025-fw_11.27-robot_sim/
Observe that it prints metrics like
Linearity(Middle)Validator:
score: 0.149987024897
metric max error in x (mm): 2.59238781369
metric max error in y (mm): 0.471314681985
metric rms error in x (mm): 1.32905315312
metric rms error in y (mm): 0.207304215494
...
Change-Id: I0aa2e5b06a3b7b33f54e1051cd97c2474bee9ba9
Reviewed-on: https://gerrit.chromium.org/gerrit/61881
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
Commit-Queue: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/tools/print_log.py
|
| 6329f91b6a5f27174f53805c6478a0757030f213 |
|
09-Jun-2013 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: Fix the tool of printing pickle log
Since the pickle log format has been changed a bit, this patch
modifies the printing tool accordingly.
BUG=chromium:248120
TEST=run the command in chroot
(cr) $ python tools/print_log.py tests/logs/lumpy/20130506_030025-fw_11.27-robot_sim/
It would show the pickle log in readable format.
$ cd /usr/local/autotest/tests/firmware_TouchMT
$ python tests/run_all_unittests.py
Change-Id: I986e151234072891aa632b017bc3123c5e2cdd6f
Reviewed-on: https://gerrit.chromium.org/gerrit/58080
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>
Commit-Queue: Joseph Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/tools/print_log.py
|
| ecc254fc00e6b3504d4f7d87abad937cf73a267d |
|
07-May-2013 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: refactor firmware_log and firmware_summary modules
Some of the code about test logs was manipulated in firmware_summary
module which made this module become messy. In this patch, we do the
refactoring by moving those code to firmware_log module and create
classes for them. In addition, we also flatten the deep hierarchy of
log dictionaries so that it is much simpler to maintain.
BUG=chromium:238039
TEST=On a chromebook
$ cd /usr/local/autotest/tests/firmware_TouchMTB
Make sure that the following unit test pass.
$ python tests/firmware_summary_unittest.py
Change-Id: Idc5a70ed28745805a4221cc20780c23da0210fb0
Reviewed-on: https://gerrit.chromium.org/gerrit/50320
Commit-Queue: Joseph Shyh-In Hwang <josephsih@chromium.org>
Reviewed-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/tools/print_log.py
|
| 4fae341b8568845295c491c38613e6e03fe99cb2 |
|
06-May-2013 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: new logs with raw data for unit tests
Re-design the unit tests for the summary modules for the purpose of a
more systematic coverage on different fw versions, different gestures,
different validators, single/multiple iterations, etc.
The raw data files are also kept so that they could be replayed
anytime when new logs need to be generated due to the change of log
format.
BUG=chromium:238039
TEST=On a chromebook
$ cd /usr/local/autotest/tests/firmware_TouchMTB
Make sure that the following unit test pass.
$ python tests/firmware_summary_unittest.py
Change-Id: Ie42ce42ac36d84bdf9e439cec5a48488f0c8b674
Reviewed-on: https://gerrit.chromium.org/gerrit/50311
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>
Commit-Queue: Joseph Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/tools/print_log.py
|