For those with an interest in exploring C++ code coverage, it is now easy to generate coverage files on try. This *does not* mean that code coverage reports are readily available, or that they will be anytime soon. This is only useful for people who are interested in creating reports themselves.
To generate coverage files, push to try with the syntax: try: -b o -p linux64-cc -u all -t none Note linux64-cc is not enabled by default, so it won't get caught by '-p all'. Here is an example try run: https://treeherder.mozilla.org/#/jobs?repo=try&revision=e212664d709b The build generated (.gcno) files can be found in the build directory. Look for "code-coverage-gcno.zip". The test generated (.gcda) files are uploaded to blobber by each individual test job. Look for "artifact uploaded: code-coverage-gcda.zip" in the bottom left after clicking on the job in treeherder. If someone figures out how to generate code coverage data on Windows/OSX, I'd be happy to take care of the scheduling pieces. Beyond that, I personally don't have any plans to work further on code coverage. If you want to take a shot at generating reports yourself, one possibility is lcov, a graphical frontend to gcov. I believe sledru and/or jcranmer may also have some scripts for doing it. Hopefully this will help get the ball rolling. Let me know if you have any questions, Andrew _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
