Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop a prototype implementation for source-based coverage report generation #43

Closed
adpaco-aws opened this issue Apr 13, 2021 · 3 comments
Assignees
Labels
[C] Feature / Enhancement A new feature request or enhancement to an existing feature.

Comments

@adpaco-aws
Copy link
Contributor

Source-based coverage report generation is an experimental feature of the Rust compiler that we need to explore further. A prototype implementation will allow us to discover any limitations that may influence the way we plan to structure the RMC testing suite.

@adpaco-aws adpaco-aws added Area: testing [C] Feature / Enhancement A new feature request or enhancement to an existing feature. T-High Priority Tag issues that have high priority labels Apr 14, 2021
@adpaco-aws adpaco-aws self-assigned this Apr 14, 2021
celinval referenced this issue in celinval/kani-dev Nov 16, 2021
Document size/align of SIMD types
@adpaco-aws adpaco-aws removed the T-High Priority Tag issues that have high priority label Nov 15, 2022
@celinval
Copy link
Contributor

https://doc.rust-lang.org/rustc/instrument-coverage.html

@adpaco-aws
Copy link
Contributor Author

Thanks, @celinval! Should try this some time, last time it was still an unstable option 😬

@adpaco-aws
Copy link
Contributor Author

I recall that, when I opened this issue, I wanted to report source-based coverage FOR source code in Kani. In other words, I wanted to use the coverage feature in the Rust compiler to obtain coverage reports for the kani compiler, its driver, etc. whenever we ran our tests, to ensure that we were covering all cases we were expecting to cover.

This shouldn't be very difficult to achieve now that the coverage feature is more mature, but it doesn't seem to be a priority for us. Otherwise, this is essentially a duplicate of #2640. For that reason, I'm closing this issue until we decide to obtain coverage metrics for Kani itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[C] Feature / Enhancement A new feature request or enhancement to an existing feature.
Projects
None yet
Development

No branches or pull requests

2 participants