Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Console tool, limit memory usage of NCrunch.exe?

    Is this being used in the context of a large solution with high code coverage density? Such a scenario can make NCrunch especially hungry. The bulk of the engine's memory consumption comes from its code coverage indexing. We need to individually track and efficiently index every line covered by…

    19 Jun 2018 01:11 UTC

  2. Console tool, is setting "Analyse line execution times" used?

    Actually, this setting IS used by the console tool. Though it's probably entirely ineffective, since right now we don't have any way to actually report the performance data. It might be wise to turn it off in your console tool configuration.

    19 Jun 2018 01:07 UTC

  3. Optimize reuse of TestHost*.exe processes

    Thanks for sharing this problem. Is there any chance you could submit a bug report? The volume of log data here might reduce the effectiveness of the bug report system, but there's still a chance I might be able to find useful information in there. Are you making use of any NCrunch.Framework at…

    16 Jun 2018 00:54 UTC

  4. NCrunch was unable to restore Nuget packages required to build a test environment for this project

    [quote=soadyp;12342]is there a close ticket option. ? If so feel free to close. I just couldnt see it.[/quote] I'm glad you managed to solve this. For a bit of background, this is a step NCrunch does to restore packages that it needs internally if it can't find the packages already installed in …

    16 Jun 2018 00:51 UTC

  5. Console tool, "MaxNumberOfProcessingThreads" vs CPU cores assigned to NCrunch ?

    The CPUCoresAssignedToX settings are only applicable when using NCrunch inside Visual Studio. When working using the console tool or a grid node, these settings are completely ignored. The NCrunch console tool does not have any CPU core affinity assigned to it (at least, not by its own code). Thi…

    15 Jun 2018 06:15 UTC

  6. Processing Tasks status vs "Max number of processing threads"

    Core Load tends to be increased by the following: - Keeping the UI updated with things going on in the engine - Merging results from the test runs (more concurrent test runs means more merge work required) - The risk/progress bar - Updating the processing queue with new tests that need to be r…

    14 Jun 2018 12:34 UTC

  7. Console tool, tests queued for passive execution results in no run tests?

    I wouldn't take the queue messages in the log too seriously. The console tool is an adaptation of the NCrunch engine designed to run without a UI, and as such it has a workflow logic that reflects a situation where state changes made to the engine happen progressively through the run. I suspect in…

    14 Jun 2018 10:20 UTC

  8. Console execution troubles

    Hi Bernd, If possible, I'd suggest creating the configuration file using the NCrunch GUI, as it can be difficult to troubleshoot if it doesn't match the tool's rather strict expectations. To ignore the component, you'll need to set the 'IgnoreThisComponentCompletely' setting to 'True', i.e.: <…

    14 Jun 2018 10:15 UTC

  9. Processing Tasks status vs "Max number of processing threads"

    The Processing Tasks on this view is the sum of all processing threads across your grid, which naturally includes your local processors and all those available on remote nodes. NCrunch coordinates all engine activity using a single thread. This is done for keeping complexity under control, and f…

    14 Jun 2018 10:11 UTC

  10. Capabilities for a grid node in NCrunch window?

    Right now there are only three ways to tell this: 1. Using the detailed logs. I'm not sure if it's available in the client-side log. 2. Using the configuration tool on the grid node server 3. By digging through the grid server registry So I guess the simple answer is that we don't have an e…

    13 Jun 2018 19:34 UTC

  11. Hot to avoid ConsoleTool error in TC: NCrunch result: TestsNotRun

    [quote=GreenMoose;12324]Just noticed there was a new command line switch [b]/TeamCityDisableTestNotRunFailureReporting[/b] which worked out great! [/quote] Yes! Sorry I'd forgotten that we'd added this one.

    13 Jun 2018 19:32 UTC

  12. NCrunch_VS2017_3.17.0.2.msi flagged as Trojan:Win32/Sprisky.V!cl

    Thanks for sharing this. I've submitted this to MS as a false positive. With malware spiraling out of control globally, scanners are getting more and more aggressive. Managing false positives is becoming more challenging all the time..

    13 Jun 2018 19:30 UTC

  13. ncrunch.exe /VS switch for a grid node?

    The grid nodes don't have this switch implemented, because they are designed to use whichever version of VS is being used inside the NCrunch client (whether this is the console tool or the VS plugin). Note that this will only work correctly if the grid node has the same tool versions installed as…

    13 Jun 2018 09:44 UTC

  14. Run issue with async method

    Thanks for sharing this problem. Your sample solution was a huge help in quickly identifying the issue. This has been caused by a small change in the way that the .NET Core compiler handles async methods. Would you be interested in trying the build below? This includes a targeted fix: [ur…

    13 Jun 2018 05:28 UTC

  15. Console execution troubles

    Thanks Bernd. Do you have Visual Studio installed on your build agent? If so, does it run correctly or report a meaningful error? The error is usually written to the log of the console tool, though it may be easier to find it in the NCrunch UI under VS. I expect this is probably security/env…

    11 Jun 2018 11:39 UTC

  16. Hot to avoid ConsoleTool error in TC: NCrunch result: TestsNotRun

    [quote=GreenMoose;12308] But it isn't the exit code that is the problem (which is #0), but it is the error reported by NCRunch as a TC service message.[/quote] Sorry, I didn't realise that was the case. I don't think this is what we should be doing here. We'll take a look at it and will see wh…

    08 Jun 2018 12:53 UTC

  17. NCrunch build breaks when building with SourceLink

    This is probably due to the way the MSBuild binding system works for PackageReferences. To my knowledge, the PackageReference declaration doesn't really get used during the build of a project. Instead, it gets used to create the files under the 'obj' directory (specifically project.assets.json).…

    08 Jun 2018 11:55 UTC

  18. Console tool and impacted tests, failed tests becomes ignored?

    Where tests are excluded using the 'Tests to execute automatically' filter, the engine won't queue them for execution. Thus they won't have a result reported by the run as they also aren't considered to be 'ignored'. I guess this is probably also related to your other question, since essentially t…

    08 Jun 2018 11:46 UTC

  19. Hot to avoid ConsoleTool error in TC: NCrunch result: TestsNotRun

    There isn't any built-in way of doing this, other than making sure all the tests get run (perhaps through the 'ignored tests' configuration). I've noticed an oversight here in that tests marked as explicit will never be run by the console tool, and therefore will cause this result. This can ac…

    08 Jun 2018 11:39 UTC

  20. Ncrunch does not copy empty folder to it's workspace.

    Ahh, sorry I just realised I missed that the folder was empty. Yes, this would be a known constraint. NCrunch identifies file dependencies using MSBuild, so if there is no file in the folder, it won't be represented when the project is loaded. The easiest way to work around this is to just add …

    06 Jun 2018 19:55 UTC