Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. NCrunch tests fail randomly

    Hi, thanks for posting. NCrunch runs tests automatically using the code straight out of memory. The saving of code to disk is not generally a trigger for NCrunch to run tests. Do you experience this problem also with other runners?

  2. Dll not in ncrunch folder

    When I run the tests locally, they all pass. I can't seem to find the VerifyAnalyzerAsync method in the code you've linked to above. Can you confirm whether the setting I described above has any impact on the resolution issue?

  3. Dll not in ncrunch folder

    Hi, thanks for posting. Can you share any more specific details about how the DLL is being referenced? Is this using Assembly.LoadFrom? Sorry, I took a quick look through the projects in the link you provided but couldn't find the reference. Have you tried turning on the 'Copy referenced ass…

  4. Core assignment backwards?

    Thanks for confirming this. I believe I owe you an apology. When advising you to give NCrunch a single core, I forgot entirely about VBCSCompiler.exe, which as described is shared by both VS and NCrunch. This process has always been somewhat of a troublemaker when it comes to thread affinity. …

  5. Core assignment backwards?

    Thanks for sharing this. Can you try the following and see if this affects your results? 1. Start VS and enable NCrunch 2. Ensure all work has finished (i.e. everything is idle) 3. Open task manager, look for the process called 'VBCSCompiler.exe'. Forcefully terminate it. 4. Rebuild your p…

  6. Grid Only Mode - CPU Core Assignment

    Hi, thanks for posting. You've set things up correctly for grid only mode. It's worth noting that turning off the local node in the distributed processing window is by itself enough (the changing of the max processing threads is optional). When in grid only node, the CPU affinity settings for…

  7. Core assignment with P-Cores / E-Cores

    We've been experimenting with this ourselves, having recently moved to CPU with this architecture. The NCrunch settings wizard is ignorant of the characteristics of the cores, so it's probably best to set this manually in the configuration window. Assuming you're running VS2022, I would recomm…

  8. When debugging C++ files are opened from within the BuildSystem directory in the VS editor

    Hi, thanks for sharing this. This is a known issue. Unfortunately, we don't have a way to solve it without introducing an instrumentation system for compiled C++ binaries (which is probably about 2+ years of work). When working in .NET based languages (i.e. C#), we are able to rewrite the PDB f…

  9. .NET8 Preview 7

    Hi Dan, Thanks for sharing this issue. As this platform is still in a preview state, we haven't done any work yet to get NCrunch running on .NET8. We'll be posting an update to address any issues when the platform is fully released.

  10. See test duration while it is running?

    Hi, thanks for posting. We don't have this ability right now. It's something I wanted to add a while back, since there's no technical reason for why it couldn't be added (outside of performance constraints), but it's quite a big task to really do it properly. The best thing I can suggest woul…

  11. Code with dynamic loading doesn't work as expected on grid nodes

    Hi Sam, The grid nodes are designed to operate with the same structure as the NCrunch client, in that they have a replica of your solution and they separate the projects into workspaces. All build, test, and dependency handling logic is the same. Where the nodes are different from the client …

  12. Blazor WASM project build fails

    Thanks for sending this through. I've reproduced the problem exactly as you've described it. The problem is caused by a recent change in VS that causes Blazor WASM project builds to break whenever they are built with SelfContained=false. From what I understand, this type of project isn't someth…

  13. Blazor WASM project build fails

    Hi, thanks for sharing these details. Is this a problem you're able to reproduce with a sample solution that you can share with me? If so, are you able to submit it through the [url=https://www.ncrunch.net/support/contact]contact form[/url]?

  14. System.ArgumentOutOfRangeException: Arrays larger than 2GB are not supported.

    Hi, thanks for sharing this issue. I believe this to be a compatibility problem in NCrunch's assembly parsing system. Somehow, the size/structure of the assembly PDB it's trying to load is different to what it can handle. I've yet to manage to produce such a situation with a test assembly in …

  15. Trace Window Copy

    [quote=mgrundner;16795] Thanks and sorry for bothering you.[/quote] Not a problem. I do actually think that something is going on here, I just haven't myself been able to pin it down. I have had problems copy/pasting from this window myself in the past... But can never reproduce it when I'm …

  16. Trace Window Copy

    Hi Manuel, Ctrl+C should work here (I understand there is no context menu). If you try Ctrl+A, then Ctrl+C, does this copy all the text?

  17. Tests Window not displaying correctly VS 2022

    Hi, thanks for sharing this issue. This looks like an initialisation problem. NCrunch isn't completing its initialisation properly, so the toolbar options aren't showing (and the engine is likely dead). Could you try the removal and [url=https://www.ncrunch.net/documentation/troubleshooting_i…

  18. Run Tests explicit in "VisualStudio" compatible way

    Hi Manuel, Thanks for posting, and I apologise for the clear frustation that you've experienced here. I think that what you're asking for is whether NCrunch could be adjusted to run tests in the same manner as VS (or other test runners) by simply using the binaries that are output from the for…

  19. NCrunch installation on VS2022 not picked up by VS2022 Preview

    Hi, thanks for sharing this issue. I recommend trying to [url=https://www.ncrunch.net/documentation/manual-installation-instructions]install NCrunch manually[/url]. Most likely it's having trouble determining the install path of the preview tooling.

  20. Grid task capacity and task queue

    Thanks for sending through the bug report. This looks to be a deployment/version issue. It seems you're running on 4.18.0.1, which was an earlier version of v4.18 that didn't include the fix for this. Could you try re-running the installer from the download page? The correct version should be …