We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We currently rely only on the file name to detect duplicates of coverage files.
During parallel run of tests, coverage files might be the same name, but not the same content (they are located in different guids folders).
We need to find a way to improve this detection.
For reference : https://community.sonarsource.com/t/flaky-code-coverage-with-net-core-test-task-in-azure-devops/22519/3
The text was updated successfully, but these errors were encountered:
Created a PR (#849) that should address this issue. Please have a look if you have time. Any feedback is appreciated.
Sorry, something went wrong.
No branches or pull requests
We currently rely only on the file name to detect duplicates of coverage files.
During parallel run of tests, coverage files might be the same name, but not the same content (they are located in different guids folders).
We need to find a way to improve this detection.
For reference : https://community.sonarsource.com/t/flaky-code-coverage-with-net-core-test-task-in-azure-devops/22519/3
The text was updated successfully, but these errors were encountered: