Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. NUnit 3 and OneTimeSetUpAttribute

    Hi, this issue was resolved a very long time ago. Is it possible you're encountering a different issue entirely? Note that because of NCrunch's batching mechanics, it's possible that NUnit mechanisms to initialise an 'Assembly' prior to execute can be executed multiple times per process. See …

    18 Oct 2016 21:52 UTC

  2. "Run all visible tests" != "Run all tests" behavior

    [quote=SeriousM;9317] I know you hate this question but do you have an eta for that? [/quote] Because this isn't a serious problem, any fix for it will likely be rolled into the next release. The next expected release at the moment is V3 due in a few weeks time. [quote=SeriousM;9317] Is th…

    18 Oct 2016 11:18 UTC

  3. ncrunch console tool - Common Language Runtime detected an invalid program

    Hi, thanks for sharing this issue. This is caused by a compatibility issue between NCrunch's instrumentation and exception filters. A fix for this has been released in v2.27. Upgrading the console tool to the latest version should solve this problem.

    17 Oct 2016 21:16 UTC

  4. Satellite assemblies from nuget package

    [quote=CsabaFabian;9310] That is correct. It is an "implicit reference", inherited from the reference to the main localization assembly. But it's an implicit reference with well defined rules: https://msdn.microsoft.com/en-us/library/21a15yht(v=vs.110).aspx [/quote] Excellent. I wasn't aware o…

    16 Oct 2016 23:17 UTC

  5. Console Tool never exits

    Good to hear that the build isn't hanging now, though as you've mentioned, this doesn't completely add up. I have a feeling that we haven't seen the last of this problem. If you see the problem start appearing again, it may be worth trying to recreate it in a debug session so you can figure out …

    16 Oct 2016 23:15 UTC

  6. Satellite assemblies from nuget package

    Hi Csaba, I'm glad you found a workaround that allows you to get NCrunch working in this scenario, though I'm not sure what change could be made to NCrunch to handle such a situation automatically. If I understand this situation correctly, the X.Y.Location.resources.dll file is referenced impl…

    16 Oct 2016 21:38 UTC

  7. Console Tool never exits

    Hi Csaba, Thanks for sending through the node logs for this run. I wasn't able to find any data in the log that showed this test finished its execution on the grid node. According to the log, the test execution started at 15:14:45 and the thread never came back. I suspect that something is…

    16 Oct 2016 00:09 UTC

  8. Console Tool never exits

    Thanks for sending through the log. According to the log, the console tool is not terminating the run because there is a task still being processed. This could be one of the following: 1. A test that is taking an extraordinary long time to execute. Although NCrunch does have timeout settin…

    14 Oct 2016 22:57 UTC

  9. "Run all visible tests" != "Run all tests" behavior

    Hi, Yes this makes sense. I'll see what I can do. Thanks for bringing it to my attention.

    14 Oct 2016 22:43 UTC

  10. Satellite assemblies from nuget package

    Hi Csaba, This specific problem is called an 'assembly co-location assumption'. Basically, your code is relying on referenced assemblies being co-located with other assemblies. NCrunch's build optimisations normally prevent this from happening because such an arrangement requires entire depende…

    14 Oct 2016 22:43 UTC

  11. csc.exe -2146232797 NullReferenceException since 2.23

    Hi, thanks for sharing this problem. I appreciate the difficulty of narrowing this down, you've done very well here. I can confirm that I can reproduce the problem exactly as described. It looks like an instrumentation issue. I'll see what I can do about getting it fixed in the next release. …

    14 Oct 2016 22:34 UTC

  12. Unable to find a usable version of MSBuild on this machine

    Hi, thanks for sharing this issue. When NCrunch searches for MSBuild under VS2013, it looks for the following assembly in your GAC: Microsoft.Build, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL If the assembly cannot be found, NCrunch will t…

    14 Oct 2016 22:23 UTC

  13. Console Tool never exits

    [quote=CsabaFabian;9295]Remco, I wouldn't post the log file publicly but I would be happy enough to send it to you privately, if you would like that?[/quote] That would really be great. The log file from the grid node that has hung would also be really useful if you're able to dig it up. You ca…

    14 Oct 2016 10:44 UTC

  14. Console Tool never exits

    It's possible that this is then actually an error handling problem on the node itself. If a node picked up some work from the client, then bugged out and failed to 'return' the work in any kind of state, the client would wait forever and the node would just sit in its failed state. Do you have a…

    14 Oct 2016 08:52 UTC

  15. Unable to cast object of type 'STATestCase' to type 'Xunit.Sdk.XunitTestCase'.

    Hi, thanks for sharing this problem. This change has recently been requested and it seems to be getting quite popular (see [dead link]). It may actually be as simple as just switching to the interface. I'll need to investigate further. Toolsets that implement their own tests under the hood c…

    13 Oct 2016 22:13 UTC

  16. How to fill TestSelectorExpression for ncrunch console?

    Hi, thanks for posting! At the moment, this isn't possible. Only simple scalar parameters can be passed into the test run via the command line. If there are certain tests you wish to ignore during a console test run, the best way to handle this is to create a custom engine mode that chooses onl…

    13 Oct 2016 22:05 UTC

  17. Console Tool never exits

    This is a good catch and I can see how this would happen. When a client has work in the queue that it thinks can be processed by a grid node but the grid node is not working properly, the client will wait until the grid node becomes available and executes the work before it considers the run to be …

    13 Oct 2016 22:02 UTC

  18. Problems with Microsoft.TextTemplating.targets

    Hi, thanks for posting! This particular build targets takes a range of properties as input, including what appears to be lists of assembly references. I don't think it was designed with NCrunch's workspacing in mind; possibly it assumes that referenced assemblies are co-located with the project …

    13 Oct 2016 10:06 UTC

  19. Build assemblies not optimiezed

    [quote=SeriousM;9277] @ramdisk: it's already 4 gb, that should be enough for 4 running threads, right?[/quote] It really depends upon the solution. NCrunch can make several workspaces for each project in your solution, depending on your change patterns and the number of workspaces needed in p…

    12 Oct 2016 17:05 UTC

  20. Build assemblies not optimiezed

    If the code coverage is working correctly, then this is probably related to the debugger (or PDB data) rather than optimisations. Is there a pattern around which values can be evaluated when you are in a debug session? Does the debug session correctly stop at breakpoints? Regarding the RAM disk…

    11 Oct 2016 22:45 UTC