Code coverage on Android does not work amnymore |
|||||
Issue descriptionCan't get coverage to work on Chrome on Android. Problem looks to be that only sancov.map file is created on |coverage_dir| and no .sancov.raw is created. We kill each individual process matching chrome process name using adb shell kill -9. I don't think kill -9 should matter since we had that previously and also this is memory mapped files.
,
Jul 11 2016
No, GYP_DEFINES are just for show. The real work is done by GN, and it does not enable coverage. Buildbot setup needs to be fixed.
,
Jul 12 2016
https://chrome-internal-review.googlesource.com/#/c/269106/. Hopefully edge level coverage should work (after pcc@ optimizations), otherwise, will switch to func level coverage.
,
Jul 12 2016
:| sorry about that.
,
Jul 12 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/clank/internal/apps/+/acb10567fd6f5c8831be3c7e885ae61d132d7ef3 commit acb10567fd6f5c8831be3c7e885ae61d132d7ef3 Author: Abhishek Arya <aarya@google.com> Date: Tue Jul 12 00:46:14 2016
,
Jul 12 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/clank/internal/apps/+/b75d87b027acce69849f1004d2c3cb522a4c1237 commit b75d87b027acce69849f1004d2c3cb522a4c1237 Author: Abhishek Arya <aarya@google.com> Date: Tue Jul 12 01:38:16 2016
,
Jul 12 2016
Thanks Evgenii for pointing out the issue and John for lightning fast review help.
,
Jul 12 2016
https://cluster-fuzz.appspot.com/coverage?platform=ANDROID&fuzzer_name=All×tamp=2016-07-01&lower_limit=0&upper_limit=100 works, yay! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by euge...@chromium.org
, Jul 11 2016