Forum member

MatthewSteeples

147 posts

Posts by MatthewSteeples

  1. IPv6 support?

    For now we're OK to continue with IPv4, but I wanted to bring it to your attention. The main reason we noticed it is that we run a split-tunnel VPN, with DNS queries carried out by the user's ISP. In this instance our user's ISP (in what I assume is an effort to increase security) doesn't resolve ad…

    20 Jul 2020 15:02 UTC

  2. IPv6 support?

    We're looking at disabling IPv4 on our VPN tunnels, but NCrunch doesn't appear to want to connect over IPv6. Looking at Resource Monitor the Grid Nodes appear to be listening on v6 addresses, but the client in Visual Studio won't accept IPv6 addresses in the config, or resolve them if the DNS entrie…

    17 Jul 2020 18:06 UTC

  3. Test coverage dots show wrong tests

    Thanks for getting back to us. That's probably not going to be a small change for us (our coding guidelines recommend returning the task if it's safe to do so) so we'll probably hold off until you've had a look to see if/when you might be scheduling a fix

    07 May 2020 13:25 UTC

  4. Garbage Collector mode

    Thanks for the detail. Makes perfect sense and stability is always preferable over performance. It's better to be slower and right than faster and wrong!

    07 May 2020 12:19 UTC

  5. Test coverage dots show wrong tests

    It looks to be async/await related. The test in question returns a Task (without being async), and doing some debugging yields the following: * If I debug the test just in VS (using the Test Explorer), I can hit breakpoints anywhere. * If I debug the test with NCrunch and step through, the test …

    07 May 2020 10:49 UTC

  6. Test coverage dots show wrong tests

    I cleared out the cache folder so that everything could re run (just in case) so these observations are done after that. * No messages appeared in the output window (after the initialisation message) * Not every test stops reporting coverage in the same place (there's 300 odd at the top, then i…

    29 Apr 2020 01:08 UTC

  7. Test coverage dots show wrong tests

    I'm submitting another bug report for this, because mid-test the dots seem to no longer update. We have some pretty lengthy tests (both in terms of lines of code hit and duration) and about 3/4 of the way through, the dots remain white and never turn green.

    28 Apr 2020 19:12 UTC

  8. Garbage Collector mode

    Apologies if this has already been considered, but I wondered if you'd done any profiling on using Server GC as opposed to Workstation GC for the NCrunch processes? There are some details in this [url=https://devblogs.microsoft.com/premier-developer/understanding-different-gc-modes-with-concurren…

    13 Apr 2020 20:20 UTC

  9. Test coverage dots show wrong tests

    [quote=Remco;14501]The report was full of internal exceptions indicating a major desync between the internal coverage database and your codebase.[/quote] Where is this database is stored? If the answer is where I think it is (the NCrunch Cache Storage Path) then could having 2 different branches …

    05 Mar 2020 00:26 UTC

  10. Test coverage dots show wrong tests

    This is going to be a fun one to diagnose! The summary is that if I click the coverage dot in the left hand margin, some of the tests are correctly listed, some are completely missing (even though they have been run) and some are listed as covering that line but they don't (and selecting to run the …

    04 Mar 2020 17:50 UTC

  11. ExclusivelyUses functionality when building

    Appreciate the thoughts. I've not investigated that thoroughly, but the project ships as a NuGet package so "comes with the source" effectively. I'm not sure what you mean by "project space" in this context. One thing we've considered (as the project is open source) is creating our own mini fork …

    21 Feb 2020 23:23 UTC

  12. ExclusivelyUses functionality when building

    [quote=Remco;14461]How critical is this particular build step? Is disabling it an option?[/quote] It's not a "step" as such, as it integrates as a Target with msbuild. It does spawn a third party process though (which is where I suspect the problem we experience comes from). We do run most of th…

    21 Feb 2020 23:08 UTC

  13. ExclusivelyUses functionality when building

    Is it possible to get the functionality of ExclusivelyUsesAttribute but for building a project rather than running tests? The summary is that we have a build task that runs to precompile views (using [url=https://github.com/StackExchange/StackExchange.Precompilation]this library[/url]) but I'm begin…

    21 Feb 2020 07:15 UTC

  14. External component has thrown an exception

    We're getting the following stack trace from one of our grid nodes. I'm not sure if we've changed anything recently, apart from keeping VS up to date. [quote]System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception. at nCrunch.Compiler.CilProcessing…

    27 Nov 2019 13:09 UTC

  15. NCrunch 4 - unabled to connect to Grid Node

    Maybe the tumbler was interfering with it ;) On a serious note, we sometimes see something similar. If the bandwidth is constrained too much, it seems to think that the transfer has "timed out" so it disconnects, even though it was still transferring stuff. Once it gets past the problematic file …

    08 Nov 2019 13:32 UTC

  16. NCrunch 4 - Instrumentation Mode - Optimized - Project fails to build

    Fixes it for us too. Thanks

    08 Nov 2019 08:30 UTC

  17. NCrunch 4 - Instrumentation Mode - Optimized - Project fails to build

    We get the same error (obviously for a different class!). Have also submitted a bug report

    07 Nov 2019 15:16 UTC

  18. Timeout transferring files

    Didn't want to create a new thread for this, but our clients and gridnodes (v3.31.0.3) don't seem to "share" files between each other. We're all remote, and we use Azure VMs as grid nodes. We use the "temporary" drive on the VM for NCrunch workspaces, which gets completely deleted every night. This …

    31 Oct 2019 10:29 UTC

  19. Intermittent errors on single grid node

    Looks like we had someone missing the ".NET Core Cross Platform Development" pieces in VS

    03 Sep 2019 08:32 UTC

  20. Exception using Grid Nodes (after Update to 3.29.0.7)

    Ah there may be _other_ clients on the network running an older version. I hadn't realised that I'd see exceptions from them too

    03 Sep 2019 08:09 UTC