Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Manual install instructions should probably be renewed a bit

    Thanks for the heads up here. I've fixed up the incorrect documentation references.

  2. NCrunch does not honor the max timeout and runs tests forever

    [quote=abelb;11386] So I tried installing the MSI for 2017 that you linked earlier (http://downloads.ncrunch.net/NCrunch_VS2017_3.12.0.3.msi), but it gives me an "another installation is already in progress". Possibly this is caused by me having three instances of VS2017 installed (Community, Enter…

  3. NCrunch does not honor the max timeout and runs tests forever

    The 0.5MB per test in this case comes from the code coverage maps, which at the moment seem to be allocated regardless of whether assemblies are instrumented. These are basically junks of memory that need to exist on a one-to-one basis with each test in the execution run. As the amount of code und…

  4. Visual Studio 2017 gives an error message "nCrunch package did not load correctly" at startup

    Hi, thanks for sharing this problem. You are correct in your understanding that this is caused by a configuration corruption issue. We have a fix pending for this issue in the next release, though it still isn't clear how it's possible for the config to get into this state. To reset your conf…

  5. Multiple Visual Studio versions

    Hi, thanks for posting. Licensing is per user, not per instance or machine. So one license for all versions is absolutely fine. You can use the same license key in all the different versions of VS you are using.

  6. NCrunch cannot discover tests due to serialization issues

    Hi, thanks for sharing this problem. It looks like we are missing a type in our binary serializer. From what I can determine, this will affect .NET Core projects (not .NET Framework ones). I'll make sure this gets fixed in the next release. Thanks for bringing it to my attention!

  7. GridNode Server Service loose Credentials after Update

    Hi Albert, Thanks for sharing this. Yes, there is a known problem here. The installer completely removes and reinstalls all components, which results in the service being reset to the LocalSystem account. We have a task in the backlog to change how this works, particularly as an increasing num…

  8. NCrunch without "workspaces"

    Hi, thanks for posting. Unfortunately, the workspace behaviour is hard-built into the engine itself and cannot be disabled. Often people ask why this is the case. The reason is that it is impossible for NCrunch to reliably deliver on most of its features without using workspacing. NCrunch is a…

  9. NCrunch fails to build VSIX project (packages Roslyn analyzer)

    Hi, Can you share any more information about the problem you're encountering here? VSIX projects have build steps that are different depending on the version of Visual Studio involved. Generally under NCrunch it's recommended that you actually disable these build steps because they slow down th…

  10. TestCase with too many parameters does not fail

    This is an error that's being kicked up at discovery time. At this point in the process, error capture and handling is much less sophisticated under NUnit v2. NCrunch recognises that there is a problem with the test, but the error itself isn't reported. The issue here is that NUnit v2 does not ha…

  11. TestCase with too many parameters does not fail

    Hi, can you confirm which version of NUnit and NCrunch you're using here? I see the message: Too many arguments provided, provide at most 1 arguments.

  12. NetCore2 projects don't get X on exception lines

    Ok, so this doesn't look like a simple problem to solve. Some machines don't seem to have the ability to read windows/full PDB files under .NET Core. Strangely, on these same machines, they also won't try to build to the 'full' PDB type. They can only build portable PDBs under .NET Core. It'…

  13. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    [quote=alastairs;11359] I had the solution opened from the folder on D: and a PowerShell window opened on F:, and ran `dotnet test` from that PowerShell window. [/quote] This explains a great deal. I couldn't understand why this wasn't failing every time. With the files being on different dri…

  14. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    [quote=alastairs;11357]Oh balls. Yes, that is intentional. I set up a junction point between the folders on the D: and F: drives, for a variety of reasons that basically boils down convenience driven by laziness 😂 The "different solution" I mentioned in my previous post was opened from the F: drive…

  15. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    I've done a deeper dive into the bug reports you've sent through, and I can see something quite unusual in the logs. On the log you sent through yesterday, there are projects with their obj\project.assets.json file stored on F: drive while their build output path and source files seem to be store…

  16. NCrunch does not honor the max timeout and runs tests forever

    I've figured this one out. The lost thread is caused by an OutOfMemoryException. I'm not sure how it's possible that this exception takes out only a thread and not the whole process, but it's the reason for the hang. I've found a performance issue in the NCrunch runtime code that allocates more…

  17. netcoreapp 2.0 problems

    [quote=mjnorman;11352]I'm not exactly sure why or how it got fixed, but when I changed the test project to netcoreapp1.0 then back to 2.0 and clean/rebuild, all is now working. I haven't seen the issue since![/quote] Thanks for confirming it's solved. It may have been something internal in .NET…

  18. netcoreapp 2.0 problems

    Hi, thanks for sharing this problem and for sending through your bug report. This is happening because NCrunch's .NET Core process is failing to initialise. The process explodes before any of the error handling can be established, so we don't know why its failed. Do you see this for all your …

  19. NCrunch does not honor the max timeout and runs tests forever

    Thanks for all the detailed information you've provided here, and for your effort in building the sample solution to reproduce the issue. It's going to take a while to figure this one out, so I'm going to track this internally and work on it as time allows. I hope that the 3.12.0.3 build improve…

  20. NetCore2 projects don't get X on exception lines

    Thanks, I'll take a look and will let you know when I have more information.