Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Project Build Error after upgrading to v3.x from v2.27 in VS2015

    Hi, thanks for sharing this problem. This looks to be caused by an IL arrangement in the assembly that the metadata reader isn't able to process. The exception itself looks to be downstream from the true problem ... I think this is going to be hard to track down. Are you able to narrow this d…

    18 Apr 2017 23:43 UTC

  2. Suppressing Build Successful messages in Tests window for non-test projects

    Hi, thanks for posting! At the moment, I can't think of any way to configure the Tests Window to give you such a setup. Turning off the green tests will of course hide the projects, but then you won't get the tests either. You're welcome to [url=https://ncrunch.uservoice.com]request a feature…

    18 Apr 2017 23:38 UTC

  3. NCrunch Build failure on C# 6 projects

    Hi Francois, Great find! I'm also not sure how I would detect this. But at least now I know that it's possible, which means I can advise other people when they report the problem to me. You'd be surprised at how common this is. I guess there might be something in the VS tooling that makes it …

    18 Apr 2017 23:34 UTC

  4. Renamed files losing coverage

    [quote=witchdrash;10289]That worked! Thank you very much :D[/quote] Thanks! Do let me know if you learn more about this marker duplication problem. I've very much like to fix it :)

    18 Apr 2017 11:27 UTC

  5. "The connection has been closed" on Distributed Processing

    [quote=Farami;10286]Awesome! 4.6.2 was indeed missing and installing it fixed the issue. Thank you very much for the quick help.[/quote] Great to hear! A fix for the detection issue will be in the v3.7 release, so next time we won't get a weird error like this.

    18 Apr 2017 07:54 UTC

  6. Code coverage not appearing (newbie question)

    I'm glad you managed to resolve this problem, but I'm concerned about the fact that it exists. If the engine is behaving normally, the ncrunch comments shouldn't create this kind of behaviour. Please do let me know if you find a way to reproduce this.

    18 Apr 2017 07:54 UTC

  7. Processing Queue Times: What do they mean?

    [quote=Grendil;10281] I've used that too, however I've appreciated the tabular view in the Processing Queue for reviewing a lot of NCrunch behavior (both tests and build/analyse steps) at once. Are the test execution times listed in the Tests window "valid" for performance analysis? (It is a bit l…

    17 Apr 2017 23:50 UTC

  8. Code coverage not appearing (newbie question)

    [quote=Grendil;10279] [quote=Remco;10278]This documentation page is also worth a read: [url=http://www.ncrunch.net/documentation/troubleshooting_missing-code-coverage]Missing Code Coverage[/url].[/quote]I read through that. It was interesting reading, but unfortunately it didn't clear me up. It s…

    17 Apr 2017 23:41 UTC

  9. Code coverage not appearing (newbie question)

    Hi, thanks for posting. Which engine mode do you usually work in? If you're using 'Run impacted tests automatically, others manually', and you haven't changed your physical code since you used the coverage suppression markers, it's quite possible your coverage data is out of date and you just ne…

    17 Apr 2017 11:12 UTC

  10. Processing Queue Times: What do they mean?

    Hi, thanks for posting. The processing queue isn't really designed for this kind of performance analysis. Instead, I suggest you use this feature: [url=http://www.ncrunch.net/documentation/reference_global-configuration_track-engine-performance]http://www.ncrunch.net/documentation/reference_glob…

    17 Apr 2017 11:06 UTC

  11. Tests not running in signed assemblies/with security transparency

    Thanks for sharing this. I haven't yet managed to reproduce the security issue, but I assume that this is tied to the nCrunch.TestRuntime.DotNetCore assembly not being signed. It appears that this assembly really should be signed in the same way as its sibling (nCrunch.TestRuntime.dll). I've se…

    17 Apr 2017 11:00 UTC

  12. Tests not running in signed assemblies/with security transparency

    It looks like this is coming from the csproj under test, assuming that this is the assembly containing the CsvReader class. If you could share the contents of the .csproj, that would be extremely helpful.

    15 Apr 2017 10:06 UTC

  13. Tests not running in signed assemblies/with security transparency

    Thanks for sharing this issue. When NCrunch instruments your code, it adds a reference to nCrunch.TestRuntime.DotNetCore. This is not a signed assembly, which usually isn't a problem for .NET projects. How has this project been configured? Is there any chance you can share its XML with me?

    15 Apr 2017 08:55 UTC

  14. Renamed files losing coverage

    Thanks. Did clearing the cache file resolve the other problem? I've also had another user report the duplication of coverage markers. This looks to be an issue with the coverage bar mounting system. I haven't pinned it down yet. Are you able to reproduce this? If so, could you submit a bug r…

    15 Apr 2017 08:54 UTC

  15. "The connection has been closed" on Distributed Processing

    Thanks for sending through the log. This error message is a bit misleading. The connection problem isn't between your client machine and the grid node, it's between the grid node and its build runner host. When the grid node attempts to run nCrunch.BuildHost462.x86.exe and hook up an IPC connec…

    14 Apr 2017 00:05 UTC

  16. Renamed files losing coverage

    Hi, thanks for sharing this problem. Can you try deleting the contents of the _NCrunch_SOLUTION directory (adjacent to your solution file) with the engine disabled to see if this resolves the problem?

    13 Apr 2017 23:59 UTC

  17. "The connection has been closed" on Distributed Processing

    Thanks. I've taken a look at the log file in the bug report. It contains some interesting exceptions, but these are all downstream from the disconnection itself and don't appear to be the actual cause of it. The grid node seems to be synchronising successfully and starting to build the projects w…

    13 Apr 2017 11:58 UTC

  18. "The connection has been closed" on Distributed Processing

    Are you running any kind of anti-virus or firewall software on your machine that might interfere with outgoing connections? Something worth trying is also to install the grid node on your local machine, then try to connect to it via loopback connection (127.0.0.1). This would help to rule out wh…

    13 Apr 2017 11:19 UTC

  19. "The connection has been closed" on Distributed Processing

    Can you check whether the version of the grid node is consistent with the client? A simple way to be certain of this is to just re-download the installer for the latest version of both and install them.

    13 Apr 2017 11:12 UTC

  20. "The connection has been closed" on Distributed Processing

    Hi, thanks for sharing this issue. Does this seem to happen only for a specific solution? For example, does it also fail if you try to use it with a very simple dummy test solution?

    13 Apr 2017 10:00 UTC