-
Notifications
You must be signed in to change notification settings - Fork 385
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
Inconsistent coverlet execution results #1546
Comments
Are you sure that on this second machine all references can be resolved/restored?
This looks like the assemblies of |
The project uses |
Hi, could you please append |
Yes you are right. The test platform should be able to load our custom collector in this case. @MarcoRossignoli any idea what the issue could be? I never faced an issue where the collector couldn't be loaded. |
When you run directly the test dll and not the sln or csproj you have to be sure that coverlet collector is in the bin close to the so or you do
and the coverlet adapter will be in the bin thanks to https://github.com/coverlet-coverage/coverlet/blob/master/src/coverlet.collector/build/netstandard2.0/coverlet.collector.targets#L12
by default |
This issue is stale because it has been open for 3 months with no activity. |
Hey,
I've got different results with the same command line and code version, but using different machines.
The xunit project has all required libraries:
The command line:
1). The first machine works as expected and generates
TestResults\8658657e-d078-4428-8e0d-458dfae204f2\coverage.cobertura.xml
2). The second executes the same command with warnings:
and doesn't generate a file.
Additional information:
First machine:
Second machine:
Why the second machine is getting the error? How to fix it?
Off topic question: It seems Gitlab can't use big files to show coverage visualization. Is it possible somehow to split coverage files to smaller parts? Does coverlet has this feature?
The text was updated successfully, but these errors were encountered: