-
Notifications
You must be signed in to change notification settings - Fork 19
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
nunit3-console with altcover 0% coverage #47
Comments
Looks like the coverage results aren't being properly flushed to disk on process termination; the same underlying issue as #42 |
release/v4.0.659 (that fixed #42) does not fix this issue |
Actually, issue #42 was re-opened a couple of weeks before this issue was raised. Getting a repro on that is next on my list when I get a chance to resume work on this project. |
Sorry for misleading comment. What i meant to say was: |
As the only change near the relevant code between 4.0.659 and 5.0.663 was a change in the static linkage of the F# core assembly, the original "fix" may have been more a "working by coincidence". Given that the whole system relies on any outstanding data being flushed during the process shutdown handler, I can see a possibility where very small or very large programs-under-test work, but moderately sized ones fail with zero coverage, so I need to test that hypothesis. |
I've not been able to get any reliable repro, but I have done some tuning on the recording side in release 5.0.665, which may ameliorate this problem. |
Thank you so far for your effort. Unfortunately 5.0.665 does not fix this particular issue. |
I was afraid that I wouldn't have fixed it; I have a very intermittent case which showed up for the first time in a while after I'd made the release. I'm not seeing your invite anywhere obvious from my side, though. |
The invite appeared a mailbox sub-folder, rather than anywhere on my GitHub profile. I hadn't been expecting that. |
Thank you for that. It reproduces on Windows. |
The first thing I noticed in looking at the coverage.xml file was that every assembly was marked I proceeded to investigate by the following steps
|
Thank you very much for resolving my misconfiguration. Have a great day sir! |
FWIW, the issue in point 5 of my comment of the 8th Feb 2019 is belatedly resolved -- the manual copy of the x86 and x64 folders is no longer needed, as this is done automatically since today's release of v8.2.825; at the time I was too busy focussing on the zero coverage issue to heed my own words about this being a limitation. |
For some strange reason i get 0% coverage with altocover (monocov reports 90%). Am i missing something? Any hints would be greatly appreciated.
altcover.5.0.663
MacOSX 17.7.0.0
CLR Version: 4.0.30319.42000
Step 1: create pcl and nunit test dll
Step 2
Step 3
Output:
Generated files:
coverage xml looks fine
Step 4:
Output:
The text was updated successfully, but these errors were encountered: