Support code coverage builds on Android
Categories
(Testing :: Code Coverage, enhancement)
Tracking
(firefox157 fixed)
| Tracking | Status | |
|---|---|---|
| firefox157 | --- | fixed |
People
(Reporter: marco, Assigned: nicolas.guichard)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file, 5 external files)
|
7.00 KB,
patch
|
Details | Diff | Splinter Review |
Comment 1•9 years ago
|
||
| Reporter | ||
Comment 2•9 years ago
|
||
Comment 3•9 years ago
|
||
| Reporter | ||
Comment 4•8 years ago
|
||
Comment 5•8 years ago
|
||
| Reporter | ||
Comment 6•8 years ago
|
||
Updated•4 years ago
|
Comment 7•3 months ago
|
||
Looks like we had ccov and then removed it? Right now we don't get C++ coverage from Android - e.g. widget/android/nsAppShell.cpp gets zero coverage data.
| Assignee | ||
Comment 8•2 months ago
|
||
Java code coverage was removed in bug 1536044 because it was broken. We
still want to have at least C++ coverage for Android so this removes
the Java leftovers to re-enable the C++ coverage in the next commit.
Updated•2 months ago
|
| Assignee | ||
Comment 9•2 months ago
|
||
This only enables code coverage for the C++ bits for now.
For Rust I think we would need to add a -dev toolchain for Android to
be able to build with -Zprofile.
For Java we probably need something like JaCoCo.
| Assignee | ||
Comment 10•2 months ago
|
||
x.py takes a single comma-separated --target argument
| Assignee | ||
Comment 11•2 months ago
|
||
Instrumenting Rust code to gather test coverage data currently requires
compiling with -Zprofile which requires building our own patched Rust
toolchain.
Updated•1 month ago
|
Updated•1 month ago
|
Comment 12•1 month ago
|
||
Comment 13•1 month ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/6606f60833f6
https://hg.mozilla.org/mozilla-central/rev/189e77457843
https://hg.mozilla.org/mozilla-central/rev/260a6d407689
https://hg.mozilla.org/mozilla-central/rev/e5524d571767
Comment 14•1 month ago
|
||
| bugherder | ||
| Assignee | ||
Comment 15•1 month ago
|
||
I missed something and the coverage-instrumented tests aren't actually being run on mozilla-central pushes yet. target_tasks_mozilla_central in target_tasks.py appears to be filtering them out.
Updated•1 month ago
|
| Assignee | ||
Comment 16•1 month ago
|
||
In my Try runs the tests ran but they didn't once my changes landed in
m-c. It appears they were filtered out here.
Comment 17•1 month ago
|
||
Comment 18•1 month ago
|
||
| bugherder | ||
Comment 19•1 month ago
|
||
| bugherder | ||
Description
•