travis-cargo currently cannot upload / generate code coverage information for documentation tests #36956
Labels
C-feature-request
Category: A feature request, i.e: not implemented / a PR.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
Comments
steveklabnik
added
the
T-rustdoc
steveklabnik
added
T-dev-tools
Mark-Simulacrum
added
the
C-feature-request
|
Triage: I don't personally use these features; @gnzlbg are you still seeing this? |
|
I can try, but I don't think anything has happened upstream to support this? cc @QuietMisdreavus I've seen rustdoc can now output the percentage of documented APIs, but that is different from actually being able to run the doc-tests with code-coverage instrumentation, and output the instrumentation results to a meaningful place, or to provide some way that cargo-travis could use to run the doc tests with external code coverage sampling (maybe this would need a custom test runner?). |
ehuss
removed
the
T-dev-tools
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@alexcrichton mentioned in this issue that this might be a bug in
rustdoc --test. Currently it is not possible to generate code coverage information from documentation tests. This results in either wrong coverage information being generated (when some functionality is tested exclusively in documentation tests). The current workarounds are unfortunately to either duplicate documentation tests into module tests to generate correct code coverage information, or to "accept" wrong code coverage information in e.g. coveralls.The text was updated successfully, but these errors were encountered: