Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. System.ArgumentException: An item with the same key has already been added.

    [quote=Silvenga;12876]Actually, kind of. The testing assembly having the issue is a .NetCoreApp application referencing a .NetStandard 2.0/.NetFull 3.5 project. I can submit a bug report, how would I do that?[/quote] There's an option in the 'NCrunch' menu for 'Submit Bug Report'. This sends thr…

    04 Dec 2018 01:37 UTC

  2. System.ArgumentException: An item with the same key has already been added.

    Are any of your assemblies multi-targeted at all? Note that later versions of project files actually have an implicit AssemblyName (it doesn't need to be specified in the file), but I expect that if you had two files under the same name, you'd probably know about it. It's possible there's somethin…

    03 Dec 2018 23:53 UTC

  3. "Unable to write to file while transferring snapshot to node: some-nuget-package-dll"

    The problem is caused by developer's machines having binary differences between the Nuget packages in their Nuget package cache directories (i.e. C:\Users\[My Name]\.nuget\packages). Since Nuget moved to using a user/global package cache for packages being referenced in a solution (i.e. no longer…

    03 Dec 2018 23:48 UTC

  4. System.ArgumentException: An item with the same key has already been added.

    Hi, thanks for sharing this issue. This appears to be caused by two projects in your environment having the same assembly name. Does this appear to be the case with your solution?

    03 Dec 2018 23:18 UTC

  5. "Unable to write to file while transferring snapshot to node: some-nuget-package-dll"

    [quote=Spielosoph;12865]Hello, we have the same problem with the grid node server. Server and clients have v3.22.0.1. It seems the grid node server has problem with Nuget package references (Not the old way with the packages.config). Many developers use the same grid node servers. Only on…

    01 Dec 2018 01:20 UTC

  6. Grid node stuck on initializing

    Hi, thanks for posting. It's possible somehow the node is bugging out during its bootstrap. Could you try turning on the logging feature inside the grid node's configuration tool, then checking to see if there are any exceptions in the logs?

    01 Dec 2018 01:15 UTC

  7. Code Coverage Markers Misaligned

    [quote=chonuff;12861] It happens consistently on certain files (I didn't find any that had issues that weren't repeatable), however you're absolutely right that scrolling seemed to fix the alignment issue. I also tried disabling CodeLens, and it rendered without issue. Upon re-enabling CodeLens, th…

    29 Nov 2018 00:20 UTC

  8. Problem with impacted test for "Track File Dependencies"

    [quote=GreenMoose;12858]Although... It is a real pity this very neat feature does not work with net core. Is there any plans of supporting it?[/quote] Sadly, this feature is heavily dependent on a 3rd party library that hasn't yet been updated to support .NET Core. Maybe we'll have a chance to…

    29 Nov 2018 00:08 UTC

  9. Code Coverage Markers Misaligned

    [quote=chonuff;12859]I'm seeing the same thing as Remco with the latest build in VS2017 using CodeLens. I noted that the NCrunch markers are lined up properly initially, then the CodeLens information pushes the lines downward. Unfortunately, the NCrunch markers don't follow the lines. Is it poss…

    28 Nov 2018 23:55 UTC

  10. Problem with impacted test for "Track File Dependencies"

    I expect that the .resx files likely won't trigger the impact detection using this feature, as they get accessed by the runtime prior to the test beginning its execution. Good catch on the documentation. I'll make sure this gets updated with our next release :)

    27 Nov 2018 23:14 UTC

  11. Problem with impacted test for "Track File Dependencies"

    Hi, thanks for posting. The tracking of file dependencies for the purposes of impact detection is best effort, since there's quite a few constraints around what we can easily do in this area. This feature is subject to a couple of critical conditions that I know about: 1. The files being acce…

    27 Nov 2018 00:17 UTC

  12. NChrunch 3.22.0.1 has issue with with building.

    Hi, Thanks for sharing this issue. I've reproduced it as you've described. The problem is caused by FSharp Type Providers being used in the referenced assemblies. Type Providers are a special feature native to FSharp, allowing assemblies to create implicit design-time references to other ass…

    24 Nov 2018 23:59 UTC

  13. Re-run specific tests

    The cache file is usually stored on the machine running NCrunch.exe. This file won't be stored on the grid nodes, although they do have cached data of a different kind (not relevant in this scenario). The contents of the cache file can be quite important when using the NCrunch console tool in th…

    24 Nov 2018 23:37 UTC

  14. Extra tests reported in TC.

    Hi Sam, Thanks for posting. This is behaviour as designed, because without it we have no way to report data from the fixtures themselves. It's quite common for fixture tests to report information outside their child tests. For example, trace data and code coverage data from methods like Te…

    24 Nov 2018 23:31 UTC

  15. Re-run specific tests

    Hi Sam, Thanks for posting. The best way I can think of to handle this would be to have a second engine mode that only runs tests that have been marked as failed. Once the first run completes and the intermittent tests fail, they'll be stored in the NCrunch .cache file with a failed status. …

    23 Nov 2018 23:03 UTC

  16. NCrunch Console and TeamCity muted tests

    Hi, Right now there is no option in NCrunch that will shut this off. We'd probably need to implement another configuration switch to handle it. You can [dead link].

    20 Nov 2018 20:34 UTC

  17. NCrunch does not work with MSBuild.Sdk.Extras based project.

    Hi, thanks for sharing this problem. Please note that right now Xamarin is not a supported platform under NCrunch (for building or test environments). We have performed no testing or integration in this area - [url=https://www.ncrunch.net/support/frameworks]https://www.ncrunch.net/support/framew…

    20 Nov 2018 20:18 UTC

  18. Grid Node - AccessViolationException - Protected Memory Issue

    [quote=MatthewSteeples;12831] An acceptable workaround for us is to declare the T4MVC.cs file as exempt from coverage. Is there an easy way to do that not using comments? Reason I'm asking is that the .cs file is autogenerated from a .tt file, so if we make the change manually it'll get overwritten…

    20 Nov 2018 01:17 UTC

  19. System.Runtime 4.1.2.0

    I can confirm that in this case, the problem and fix for the problem were both in the NCrunch codebase. A recent VS release (I think it was 15.7?) introduced a new build-time redirection system to try and retroactively add support for .NET Standard 2.0 in earlier versions of the .NET Framework. …

    20 Nov 2018 01:14 UTC

  20. Grid Node - AccessViolationException - Protected Memory Issue

    Hi, thanks for sharing this issue. It's interesting that this code is reporting an exception on line 0. I can see how that would lead to problems with coverage tracking. Do you know how this is happening? Are there compiler declarations in place in your generated code to redirect the line re…

    19 Nov 2018 20:04 UTC