Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Could not load file or assembly 'System.Runtime, Version=4.1.1.0...'

    Horrah! I'm glad you found the solution! Thanks for letting me know :)

    21 Sep 2017 23:44 UTC

  2. Could not load file or assembly 'System.Runtime, Version=4.1.1.0...'

    NCrunch is continuing to function in this case because the error is happening only during the analysis task, when tests are discovered. The analysis task is always run on each grid node after a build. Because only one task is actually needed to get the true list of tests, the redundancy allows t…

    21 Sep 2017 11:47 UTC

  3. When NCRunch adds instrumentation, it sometimes changes the signature of class members

    Because it involves heavy code manipulation and detailed tracking, instrumentation does come with technical limitations. It is unfortunately not possible to measure the performance of software without at some level affecting the performance itself. Because NCrunch is line-by-line, the instrumentat…

    21 Sep 2017 11:43 UTC

  4. When NCRunch adds instrumentation, it sometimes changes the signature of class members

    Thanks for sharing this problem. I think this is happening on writeback of the instrumented assembly. Probably there is some metadata here that is quite specific to F# and goes a bit wrong somewhere in the processing. Issues like this one can be quite hard to fix, so unfortunately I can't provi…

    21 Sep 2017 01:16 UTC

  5. NCrunch test duration not reporting correctly to TeamCity

    Thanks for sharing this problem. The TeamCity integration is way out of date and is due for an overhaul. I've made a note of this issue to get it addressed with the rest of the integration.

    20 Sep 2017 23:17 UTC

  6. Processing queue often empty, but *something* is running

    Sorry, I just realised my suggestion for analysing the hung tests was written in a different thread: [quote] There is a way to debug inconsistent behaviour like this. It involves implementing your own timeout mechanism around the test itself, and making a call to System.Diagnostics.Debugger.Laun…

    20 Sep 2017 23:15 UTC

  7. Could not load file or assembly 'System.Runtime, Version=4.1.1.0...'

    Sorry, it looks like I may need to ask for a code sample that can reproduce this :( This is going to be a tough one to figure out. The CLR is having an internal issue while trying to load this assembly. My experience with these sorts of problems suggests that trying to get specific information …

    20 Sep 2017 23:11 UTC

  8. Processing queue often empty, but *something* is running

    [quote=abelb;11219] It's the same project, but not precisely the same moment (I mean, when I sent the report, the queue was filled). I will try to repro that particular situation and send a report on that too. [/quote] Understood. This is the problem I feel the best equipped to solve via the b…

    20 Sep 2017 12:55 UTC

  9. Processing queue often empty, but *something* is running

    [quote=abelb;11214] Another strange behavior with this particular project is that if I run all tests, it seems to sometimes spontaneously restart my system (without any log entry in the event viewer, or blue screen). I have yet to determine whether this is caused by NCrunch or the project itself. W…

    19 Sep 2017 23:58 UTC

  10. NCrunch testrunner crashes on a Debugger.Break()

    This is handled by the O/S itself. I guess it's possible for NCrunch to rip these calls out during instrumentation, but sometimes they can be useful if you want to hook a debugger onto a running session (which I believe is often the intention). I think it would be rather messy or even detrimenta…

    19 Sep 2017 23:51 UTC

  11. NCrunch does not honor the max timeout and runs tests forever

    NCrunch's enforcement of timeouts (under .NET Framework) is handled using ThreadAbortException. Unfortunately, this approach is not 100% reliable. There are certain low level calls that seem to be able to block it, allowing the process to be hung in these calls and preventing the timeout from prop…

    18 Sep 2017 23:52 UTC

  12. Processing queue often empty, but *something* is running

    Hi, thanks for sharing this problem. In a situation like this, the processing queue should never be empty. Something is going wrong. Could you submit a bug report after you've had this happen to you? The settings to turn on visible logging are 'Log to output window' and 'Log Verbosity'.

    18 Sep 2017 23:42 UTC

  13. NCrunch v3.11 - nCrunch.VSIntegration2017.dll could not be found.

    This is almost certainly a continuation of the file blocking problem. When the files are decompressed, windows will block every single one. If there is a single DLL that is still blocked when you try to load the package, you'll see this error or something like it. Make sure you've unblocked every…

    18 Sep 2017 09:02 UTC

  14. NCrunch v3.11 - nCrunch.VSIntegration2017.dll could not be found.

    Hi Joe, Thanks for posting. Something to check is whether the O/S is blocking access to this through its magic 'blocking' feature. Try right clicking on this file in Windows explorer and choosing Properties, then look to see if there is an option to 'Unblock' the file. If the option exists…

    18 Sep 2017 08:32 UTC

  15. NUnit3 Retry attribute

    In theory, the logic of this attribute should be handled internally by NUnit and shouldn't require any involvement from NCrunch. I can't say that I've specifically tested it, but I can't tell you any reason why it wouldn't work. I recommend giving it a try. Again, in theory, I can't think of an…

    14 Sep 2017 23:20 UTC

  16. Unable to get correct test timings using the Console Tool with TeamCity without duplicated tests

    Hi, thanks for sharing these issues. NCrunch's TeamCity integration is minimal. It's also quite out of date. Since this isn't a primary feature area of the product, it hasn't seen the same levels of attention as other areas. At the time it was implemented, the manner in which test results had …

    12 Sep 2017 23:34 UTC

  17. ConsoleTool: Not run tests if build is failing?

    [quote=GreenMoose;11196] I had this in mind as well bug figured the NCrunch workspace will be left uncleaned, does NCrunch do something smart with workspace/cachefolder leftovers so it cleans them eventually even if I simply kill the process now and then? [/quote] If the process gets killed, th…

    12 Sep 2017 09:54 UTC

  18. ConsoleTool: Not run tests if build is failing?

    There isn't anything in NCrunch that can be configured to do this. The engine will always build what it can, then run tests with whatever assemblies it managed to build. Having a separate compile step before running NCrunch is one way to do this. An alternative would be to rig something up to c…

    12 Sep 2017 07:22 UTC

  19. Configuration/UseBuildConfiguration not supported by console tool?

    [quote=ljohnston;11189]We're moving to using the console tool to do our CI testing and ran into this as well. We would like to ensure we're building in release configuration for CI but use the default elsewhere. We could (and may) use the workaround you mentioned but it seems odd that this isn't sup…

    12 Sep 2017 00:54 UTC

  20. Disable auto restoring nuget packages

    My guess would be here that because the console tool does this for each individual project, it's less efficient than doing it for the solution as a whole. Probably if you have many projects using many nuget packages, 12 minutes might even be achievable in a worst case scenario. I'm considering d…

    12 Sep 2017 00:39 UTC