The instructions seem to assume running the script from /src and
the intent is to create two directories
/tmp/coverage
/tmp/coverage_report
but the lack of a slash prefix results in the creation of...
/tmp/coverage
/src/tmp/coverage_report
Bug: None
Change-Id: Ib10050a577fc8e9494a903386d5886ccbef8aa1e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124256
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: Yun Liu <yliuyliu@google.com>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754026}
Right now Java per-CL coverage instrument everything as full code base coverage.
To only instrument class files related to affected files in a CL, we can:
1. Extract class files only related to affected source files in a jar.
2. Instrument these extracted class files.
3. Extract unaffected members from original jar.
4. Zip everything out to output path.
Bug: 1001387
Change-Id: Iaf6a75c7f8005b5d64eee22bc604f25d0c2fcd8c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1797109
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Yun Liu <yliuyliu@google.com>
Cr-Commit-Position: refs/heads/master@{#697661}
No change to logic, only docs. This is a mechanical docs change which
should not impact content (but will improve readability).
This edits some Android docs to use fenced code blocks more
consistently:
* Prefer fenced code blocks over indented code blocks
* Fix indentation issues (see coverage.md)
* Specify a language for syntax highlighting where it makes sense
(particularly, use the "gn" language where it was omitted)
R=agrieve@chromium.org
Bug: 918221
Test: Upload to gerrit > open file > click "gitiles"
Change-Id: I2a4aa292d3bd1cf67bd0a7bcfb0cb01f7b8ede98
Reviewed-on: https://chromium-review.googlesource.com/c/1451357
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#628981}
This CL is an attempt to document the rather sophisticated
use and content of .build_config files when building various
Android-specific targets with GN for Chromium.
- Add a new documentation build_config.md under
android/build/docs/
- Add documentation for the .build_config file format
itself as a Markdown document inside of
write_build_config.py to make it easier to update
the documentation along side the script in the future.
See build_config.md for extraction + visualization
instructions.
+ Add missing links to Android Build markdown files
to docs/README.md
+ Reformat coverage.md a little to make it readable.
R=agrieve@chromium.org,yfriedman@chromium.org,estevenson@chromium.org
Bug: None
Change-Id: Ic9bb61e50d578d69dea4ebc721d41feb9f68a5cb
Reviewed-on: https://chromium-review.googlesource.com/949463
Commit-Queue: David Turner <digit@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541395}
Added coverage.md file for emma code coverage instructions for both
instrumentation and junit tests.
BUG=608085
Review-Url: https://codereview.chromium.org/2031743002
Cr-Commit-Position: refs/heads/master@{#397474}
