-
Notifications
You must be signed in to change notification settings - Fork 145
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
Grcov create a sub-folder inside the same previous output folder when the output type is html #1020
Comments
I found out that |
This caught me out, and I was not using a trailing |
Same here. Using a trailing slash changes nothing. $ grcov . -s . --binary-path target/debug -t html -o ./target/debug/coverage/
$ ls ./target/debug/coverage
badges src tests coverage.json index.html
$ grcov . -s . --binary-path target/debug -t html -o ./target/debug/coverage/
$ ls ./target/debug/coverage
badges html src tests coverage.json index.html $ grcov . -s . --binary-path target/debug -t html -o ./target/debug/coverage
$ ls ./target/debug/coverage
badges src tests coverage.json index.html
$ grcov . -s . --binary-path target/debug -t html -o ./target/debug/coverage
$ ls ./target/debug/coverage
badges html src tests coverage.json index.html |
@qsantos that path does not end in |
Hello @hartwork, thank for the suggestion! Unfortunately, I still get the same behavior:
In your GitHub workflow, I only a single call to |
By the way, my own solution is to just |
@qsantos thanks for sharing these details! 👍 |
Tools version
Replication steps
Create an example project:
Generate coverage data using example tests:
Generate coverage report in HTML:
grcov --output-path=html/ --output-type=html --binary-path=target/debug/deps .
List output directory:
Re-generate coverage report
grcov --output-path=html/ --output-type=html --binary-path=target/debug/deps .
List output directory
Expected result
I was expected
grcov
to not create another folderhtml
in the output folderhtml
and to just reuse the folderhtml
by overwriting files that need to be.The text was updated successfully, but these errors were encountered: