Skip to content

Try using coverage tracking for Clippy #3986

@phansch

Description

@phansch
Member

It would be nice if we were able to gather test coverage information for Clippy.

We have an old script written by @mcarton that could be used to run kcov on Clippy. It seems like this script doesn't work currently for various reasons.

While making coverage tracking work again it might be worth to investigate tarpaulin, as well.

@felix91gr mentioned on Discord that they would like to work on coverage tracking once #3963 is done.

Activity

added
C-enhancementCategory: Enhancement of lints, like adding more cases or adding help messages
on Apr 18, 2019
changed the title [-]Try enabling coverage tracking for Clippy (again)[/-] [+]Try using coverage tracking for Clippy[/+] on Apr 18, 2019
mati865

mati865 commented on Apr 18, 2019

@mati865
Member

There is no accurate coverage available for Rust right now. rust-lang/rust#34701 is promising but probably years from being done.

ThibsG

ThibsG commented on Nov 13, 2020

@ThibsG
Contributor

Recently, improvements have been done with the use of llvm-cov (see rust-lang/rust#34701).

Zulip thread to see rendering work done by @flip1995.

To improve this rendering, one leftover question is how to exclude dependencies from the results (e.g. exclude results from .cargo and .rustup paths): maybe building deps without -Zinstrument-coverage?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-enhancementCategory: Enhancement of lints, like adding more cases or adding help messages

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @mati865@phansch@ThibsG

        Issue actions

          Try using coverage tracking for Clippy · Issue #3986 · rust-lang/rust-clippy