| Age | Commit message (Collapse) | Author |
|---|
|
BUG=none
TEST=Check repo --verify is not complaining anymore.
Change-Id: Ia90fced35f679a52c76c78ad4a2ab80fce0ce64e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/gestures/+/4300260
Reviewed-by: Harry Cutts <hcutts@chromium.org>
Code-Coverage: Harry Cutts <hcutts@chromium.org>
Commit-Queue: Gwendal Grignou <gwendal@chromium.org>
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
Tested-by: Gwendal Grignou <gwendal@chromium.org>
|
|
BUG=chromium:224451
TEST=Manually ran tool to fetch logs
Change-Id: Id5319d37e8dd6cefa5e1a69b3e84f27d84c0fa7c
Reviewed-on: https://gerrit.chromium.org/gerrit/46704
Reviewed-by: Dennis Kempin <denniskempin@chromium.org>
Commit-Queue: Andrew de los Reyes <adlr@chromium.org>
Tested-by: Andrew de los Reyes <adlr@chromium.org>
|
|
This is handy if you ever want to look at the system log.
BUG=chromium-os:35327
TEST=Tested manually; saw system log appear
Change-Id: Ic0e07777e7235f4cada136606cd6cd1b5be0fffa
Reviewed-on: https://gerrit.chromium.org/gerrit/35586
Reviewed-by: Yufeng Shen <miletus@chromium.org>
Commit-Ready: Andrew de los Reyes <adlr@chromium.org>
Tested-by: Andrew de los Reyes <adlr@chromium.org>
|
|
I'm not quite sure why the feedback report file format keeps changing,
but this change will expand the newest log formats.
BUG=chromium-os:34179
TEST=was able to expand recent R23 feedback report
Change-Id: Iff4073e9073c9affdc8e8c49fac70fe6a90c129b
Reviewed-on: https://gerrit.chromium.org/gerrit/32317
Reviewed-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
Commit-Ready: Andrew de los Reyes <adlr@chromium.org>
Tested-by: Andrew de los Reyes <adlr@chromium.org>
|
|
BUG=chromium-os:33002
TEST=tested w/ older log
Change-Id: I467e5183a185bee4e02133ac2ef75787fb595677
Reviewed-on: https://gerrit.chromium.org/gerrit/28544
Commit-Ready: Andrew de los Reyes <adlr@chromium.org>
Reviewed-by: Andrew de los Reyes <adlr@chromium.org>
Tested-by: Andrew de los Reyes <adlr@chromium.org>
|
|
This is needed when using Dennis' new regression test. The log is
written to evlog.txt.
BUG=chromium-os:32323
TEST=tested that the log was pulled and expanded
Change-Id: I5cee09b9ff391971726d95df79a55e0f2e112d70
Reviewed-on: https://gerrit.chromium.org/gerrit/26615
Reviewed-by: Dennis Kempin <denniskempin@chromium.org>
Commit-Ready: Andrew de los Reyes <adlr@chromium.org>
Tested-by: Andrew de los Reyes <adlr@chromium.org>
|
|
If the input argument to the replay_log is a directory, test all
the logs in the directory and list the test results.
BUG=chromium-os:31533
TEST=Perform the following tests inside chroot.
$ cd ~/trunk/src/platform/gestures
$ tools/replay_log --only_honor "" tools/logs/cr48
It would test all of the logs in the given direcotry, and list the
test result.
Change-Id: I6b00c9f3d173ce8573faef7b42dd6dba7bb6984f
Reviewed-on: https://gerrit.chromium.org/gerrit/24680
Commit-Ready: 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>
|
|
When downloading a log from the feedback site, if it succeeds,
assign the downloaded LOG_FILE to infile. Otherwise, the following
script cannot open the LOG_FILE for further processing.
Note that if the same command is run the 2nd time, it would execute
normally because it uses another block of statements if the LOG_FILE
already exists.
BUG=chromium-os:31516
TEST=Try the following command. It should succeed at the first time.
(cr) $ tools/replay_log --only_honor ""
https://feedback.corp.googleusercontent.com/binarydata/report-291598177-system_logs.bz2
Change-Id: I562d51b488f86b79408129b2c67610717cec4415
Reviewed-on: https://gerrit.chromium.org/gerrit/24966
Reviewed-by: Andrew de los Reyes <adlr@chromium.org>
Commit-Ready: Joseph Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
|
|
With this change, a URL can be specified on the command line. User
must have an @google.com account.
BUG=chromium-os:31516
TEST=tried it out
Change-Id: I82f9a1e961251b30267335b6325cea17e2efeb05
Reviewed-on: https://gerrit.chromium.org/gerrit/24424
Commit-Ready: Andrew de los Reyes <adlr@chromium.org>
Tested-by: Andrew de los Reyes <adlr@chromium.org>
Reviewed-by: Andrew de los Reyes <adlr@chromium.org>
|
|
We assumed that only JSON touchpad activity logs were present, but
with the new CMT logging, that's not always the case. We now grep to
get the correct file to replay.
BUG=chromium-os:29810
TEST=replayed feedback logs successfully
Change-Id: Ie0e4cd83ee454de6b0ea76479191a64cb22032d2
Reviewed-on: https://gerrit.chromium.org/gerrit/20768
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Tested-by: Andrew de los Reyes <adlr@chromium.org>
Commit-Ready: Andrew de los Reyes <adlr@chromium.org>
|
|
Just build a new chroot and realized that I had the path wrong.
BUG=chromium-os:27506
TEST=replay_log runs successfully
Change-Id: I67381fef6f2d2d7a1600ef2e922b3d02a4f57c6d
|
|
This script makes it very easy to replay an activity log. One simply
specifies the input file as the only argument and it has reasonable
defaults: only honor the currently user-settable properties in the log
file (Tap Enable, Sensitivity) and dump the output log to testlog.txt.
It also detects the input file format, which can be any of:
- system report tarball from https://feedback/
- gzip compressed log (from user home logs dir)
- uncompressed log
BUG=chromium-os:26799
TEST=replayed many logs with this script
Change-Id: Id8b434cebd8958fec6e09844ca8e157691b34cf8
|
