-
Notifications
You must be signed in to change notification settings - Fork 388
Coverlet fails on concurrent runs #950
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
Can you explain how you use coverlet command?Run parallel(on same test file) |
Dll is always the same. coverlet <some-dll> --target dotnet --targetargs "exec <some-dll>" --include-test-assembly <other-options> Maybe there is some workaround for our case? |
mmm at the moment no...you need to run tasks in a sequential way. Or use some other way like collectors and run all different test project in parallel, are you running on .NET Framework or .NET Core?
I don't know ho dotcover works, just for curiosity can you attach dotcover run script? |
We run .NET Core, but our dll is not test suite, we run real application under coverage, tests written on Python, one test can use several instances of application (for example one instance can be web, second instance can be rabbitmq consumer). After all we merge reports from all application runs in single report. Our dotcover command:
|
You could try something like that #781 (comment) |
What do you mean by "different copy of artifacts"? |
Build one time...move artifacts in different folders fold1/fold2/fold3 and run in parallel |
OK, I understand, thanks! |
Hello!
We write functional tests on python and want to collect coverage from our dotnet applications. Tests start several instances of same dll with different parameters. We used dotcover before and everything was fine. But with coverlet we get such error:
coverlet.console version: 1.7.0.0
The text was updated successfully, but these errors were encountered: