Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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

  11. 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

  12. 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

  13. 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

  14. 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

  15. 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

  16. Console execution troubles

    Hi, thanks for sharing this issue. The problem you're experiencing with the package restore is caused by the 'msbuild /t:Restore' failing when this step is executed by the console tool. It's possible you have the machine locked down so it's unable to access Nuget or there is otherwise something …

    06 Jun 2018 19:51 UTC

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

    Hi Daniel, Thanks for sharing this problem. Could you clarify the purpose of this pre-build event? Is this trying to copy files from another project in your solution? If so, this may break [url=https://www.ncrunch.net/documentation/considerations-and-constraints_project-atomicity]NCrunch's pro…

    06 Jun 2018 11:57 UTC

  18. TeamCity distributed NCrunch is very slow

    [quote=robert-j-engdahl;12295] It is great that you have auto-batch size already. I agree setting a default would be redundant. How will tests with unknown execution times be handled in that setup, and could [AutoData] cause known tests to seem unkown?[/quote] By default, NCrunch considers a t…

    06 Jun 2018 11:52 UTC

  19. TeamCity distributed NCrunch is very slow

    The 'batching' of tests is very dynamic, as NCrunch will try to put faster running tests into bigger batches. You'll find that if you have 1000 tests with a running time of <1ms, they'll usually all land in the same task. Slow running tests will generally end up in small batches, and very often ca…

    06 Jun 2018 10:51 UTC

  20. ASP.NET Core 2.1 integration tests

    To update everyone on this issue, we've taken a deep look at it, and it's not good. This package works by hard-baking the location of the web project into the test project's binary. So if the web project moves relative to the test project, everything breaks. Given the current design of NCrunch,…

    06 Jun 2018 06:22 UTC