-
Notifications
You must be signed in to change notification settings - Fork 389
BUG: Missing coverage #39
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
Comments
What's |
it's the logger output for dotnet test. To run my tests, I do the following:
the --logger:trx, produces the trx output file (which is vstest output format?). This is then picked up by sonarqube and processed to identify failed tests. |
@pms1969 Once again it seems we are have some of the same issues. I think it is because we are attempting to run this in a CI/CD environment. I encountered the same no output if I have the --no-build and --no-restore switch. When I removed the switch I would I get the "because it is being used by another process" issue again. I discovered if I let the process build into empty directory it would fail. When I ran a dotnet publish and specified the configuration switch to it previously run publish directory it would succeed. I have put my successful patterns below.dotnet publish src/Server.Tests/Server.Tests.csproj -c Debug dotnet publish src/Server.Tests/Server.Tests.csproj -c Release |
@sampwil Thanks. I haven't had time to circle back to this yet. Hopefully soon. I thought I'd managed to rid us of the "used by another process" problem. but apparently not. There's a newer version out, since I posted this originally, so maybe something in there fixes this. maybe not :/ I'll just have to play again and see. Unfortunately publishing, and rebuilding every time doesn't work for us. The coverage job takes neigh on 22 minutes at present. Using coverlet and linux docker instead of the current dotcover and windows, I can get the time down to 14'ish minutes. It has to be something simple. |
Moved discussion to #72 |
Just noticed this in my build pipeline
Basically, ran 144 tests, but obviously failed silently when generating the coverage file. This happened on a number of test assemblies. :-(
Any ideas what might be causing that. I've not been able to see that happen locally.
The text was updated successfully, but these errors were encountered: