Forum member

ndeslandes

22 posts

Posts by ndeslandes

  1. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    Yeah I agree. I'm sure Windows which just handle this fine. I doubt I'll notice any slowdown in VS

  2. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    Oh yeah that's a good point. I actually did mean to spread them like this, thinking it'd be good for NCrunch to get scheduled across more cores. But actually that might not be so good for things like cache locality... So I think I'll move to this setup instead: IDE: 0,1,2,3 NCrunch: 4,5,6,7,2,3 …

  3. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    [quote=Remco;18504] I can only speculate about why this was causing some of the weirdness you've found here. I'm impressed at the level of creativity you've shown in diagnosing the problem. [/quote] Haha thanks. Yeah I really had to throw my whole arsenal at this one :-) My guess is it's some…

  4. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    So yes, adding just 1 extra core to the IDE (even leaving it to NCrunch as well) stops the freeze: [code=yaml] +------------------------------------------------------------+----------------+---------------------+----------------------+ | Setting Name …

  5. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    Actually this is it!! My core re-assignments weren't saved properly. Giving Visual Studio some extra cores fixes the issue! Wow, I would have never guessed that setting would be responsible for this, and only when NCrunch is disabled for the solution !

  6. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    [quote=Remco;18499]Also, can you confirm how you have your CPU cores configured between NCrunch and VS, and whether adjusting this setting makes any difference?[/quote] Ah good point; I'm very aggressive to give NCrunch as much cores as possible: [code=yaml] +---------------------------------…

  7. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    I'm running this powershell script to keep track on when exactly MSBuild is spun up: [code=powershell] 1..100000 | % {ps *msbuild*; sleep -Milliseconds 100} [/code] This tells me clearly that MSBuild only appears [i]after[/i] the freeze, and only for about 0.7 s: [code] NPM(K) PM(M) …

  8. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    I think we're on to something with MSBuild. I do notice something very different with or without NCrunch, when I just repeatedly trigger a Clean build on my solution: [list] [*] If NCrunch is installed but disabled: MSBuild.exe is not started until after the 5-6 s freeze, and then only stays ar…

  9. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    Thanks for looking into this. I've just submitted the bug report you asked for. A few more precisions on what I've observed: [list] [*] The freeze doesn't happen if NCrunch is enabled when solution is open and then disabled, only if the solution starts with NCrunch disabled for it [*] It ha…

  10. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    No, this is what I have: * Log to output window: false * Log verbosity: Summary To be clear, the freezes disappear once I enable NCrunch! Very perplexing...

  11. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    A strange one I've been battling for the last few weeks. Applies to VS2022 or VS2026 I noticed that for a tiny number of solutions, Visual Studio would completely freeze for 5-10s whenever a new build action was kicked off for the solution; including something as simple as "Clean" repeatedly. Th…

  12. Rendering each test case for an XUnit Theory

    Out of curiosity, how come this works as expected, producing one test report per theory use case? [code=csharp] public class IntDataClass : IEnumerable<object[]> { /// <inheritdoc /> public IEnumerator<object[]> GetEnumerator() { yield return new object[] { 1, 22 }; …

  13. Support for C# source generators?

    [quote]Note that it presently isn't possible for NCrunch to instrument the source generating project or track code coverage in it.[/quote] Probably related, but another thing that's not working is that when a change is made to the generator, the "run impacted test" mode doesn't pick up the tests …

  14. Support for C# source generators?

    Great, thanks Remco! It worked fine on my solution. I'm just getting these warnings, but they don't seem to cause any issues: [quote] Microsoft.Net.Compilers Nuget package references are not currently supported by NCrunch. [/quote]

  15. Support for C# source generators?

    [quote=Remco;15497][quote=ndeslandes;15496] Yes!! We still need a self contained code sample that can work with source generators (and make NCrunch fail). It must be the latest version of the tooling. Our attempts on this side to build such a sample have so far failed. [/quote] Cool; there yo…

  16. Support for C# source generators?

    Hi @Remco, Are you still looking for a working solution with the problem? I can probably cook one up if that helps. Source generators have just been introduced in our solution, and I now find myself in the same situation as tkarlsen, with NCrunch now being simply unusable :-(.

  17. Support for VS 2019?

    I'm seeing the same problem as MatthewSteeples. The test runner windows is not showing any content. I just submitted a bug report. Hope that helps. I also have a high dpi screen with 150% scaling factor.

  18. Filtered tests are stuck in 'Pending' status

    Right on! For some reason I didn't even notice the "Tests to execute automatically" setting. Your suggestion is exactly what I needed. The tests are still marked as "Pending", but I can live with that. At least the global state now completes (ie the Stop button is grayed out, and the notification …

  19. Filtered tests are stuck in 'Pending' status

    Hi, I want to filter out "LongRunning" tests from NCrunch execution. To get that behaviour, I defined a test category "LongRunning", and setup the shared test configuration to specify that only test that don't have this category should be run: [img=https://i.imgur.com/W28TTLa.jpg]Categories[/img…

  20. Startup Error in Studio 2017

    [quote=Der-Albert.com;10380]This can be a problem of the multiple instance issue. I tried to update to 3.7.0.7 (from 3.7.0.4), but because of .NET Core 2 i also installted a preview of VS2017. NCrunch deleted itself from the normal installation, installed to the preview and call devenv.exe onl…