Forum member

slafave

13 posts

Posts by slafave

  1. Tests Window has all status colors instead of solid green

    I have additional information. The initial state of the test tree was expanded for 2 of the test projects. When I collapsed the tree, the bar turned green. Now, no matter how I load the solution, trees expanded, trees collapsed, new VS window, existing VS window, the bar is always correct to the …

  2. Tests Window has all status colors instead of solid green

    I submitted the bug report

  3. Tests Window has all status colors instead of solid green

    Yes, all the colors to show after I load my solution and all my tests are passing. I will submit the bug report.

  4. Tests Window has all status colors instead of solid green

    After I updated to 3.28.0.6, the Tests Windows is now visually misleading and actually impacting work focus. The line of color at the top used to be all green if all tests were passing. Now it is a static line of Red, Dark Red, White, and Green, which distracts me as I've trained myself to react t…

  5. dotnet.exe hosted by nCrunch.EngineHost462.x64.exe using 25% CPU doing nothing

    Found it and you were right, not an NCrunch issue. Not even a DotNetCore issue. An ancient class buried deep in a series of mocks had a timer that activated a while loop that spun over an empty array to simulate polling a queue. :-( Thanks for the help, sorry to bother you with our issues....

  6. dotnet.exe hosted by nCrunch.EngineHost462.x64.exe using 25% CPU doing nothing

    I have narrowed it down to a particular test suite. I'm enabling each test there one at a time to figure out which one causes the issue.

  7. dotnet.exe hosted by nCrunch.EngineHost462.x64.exe using 25% CPU doing nothing

    Additional info: If I close the solution but leave VS open, all NCrunch and hosted dotnet.exe processes go away, and CPU usage falls back to idle. I will upload a bug report for this state as well.

  8. dotnet.exe hosted by nCrunch.EngineHost462.x64.exe using 25% CPU doing nothing

    Additional observation: everytime I kick off another F5 debug run, NCrunch adds another hosted dotnet.exe that's consuming 25% CPU! I now have 3 hosted dotnet.exe's consuming 75% of my CPU. I am uploading a bug report in this state now.

  9. dotnet.exe hosted by nCrunch.EngineHost462.x64.exe using 25% CPU doing nothing

    An additional observation to add. When F5 Debugging, NCrunch is now hosting a second dotnet.exe host that is also consuming 25% CPU, for a total of 50% CPU consumption by NCrunch doing nothing. :) I have uploaded a bug report while in the middle of F5 debugging. No code has been changed so no…

  10. dotnet.exe hosted by nCrunch.EngineHost462.x64.exe using 25% CPU doing nothing

    I sent the bug report just now. Hopefully it is helpful. I also look at all the open file handles under the hosted dotnet.exe process. They appear to be the solution's compiled DLLs in the NCrunch cache, the Core 2.2 libs in the shared MS install location, and mu local NuGet cache. Nothing sto…

  11. dotnet.exe hosted by nCrunch.EngineHost462.x64.exe using 25% CPU doing nothing

    [img=https://1drv.ms/u/s!ApAvr87fXSU8gUYpYdiZGDus4MIO]stack dump[/img] I'll have to check the file handles on Monday when I'm back online.

  12. dotnet.exe hosted by nCrunch.EngineHost462.x64.exe using 25% CPU doing nothing

    I have a solution with 158 tests. They are all passing, they all execute in milliseconds. In the past week I noticed that NCrunch Engine was consuming 25% of my CPU time, even when I'm not doing anything in VS. NCrunch has nothing queued for execution, I'm not actively developing, all tests a…

  13. NCrunch tries to build Docker Project

    In VS2017, if you add Docker Support to a project/solution, a docker-compose.dcproj file is created a treated as a buildable project by VS. NCrunch can't build this. You need to manually exclude the project from each Solution.