Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. NCrunch 1.x, 2.x build forever

    A way you can check whether this problem is caused by mass including of files would be to leave the machine running overnight, then check the size of your NCrunch workspaces in the morning after it's done a ton of processing. If the size of the workspace directory is unbelievably big, then there ma…

  2. NCrunch crashes - can submit crash dmp file?

    Ahh sorry. I just re-read your post and realised I must have been cross-eyed (<facepalm>). A link should be no problem. Drop it through the form and I'll be happy to take a look.

  3. NCrunch crashes - can submit crash dmp file?

    That is very, very strange. The other thing I would suggest is trying to comment out or deduct parts of the code under test to see if you can narrow down what's causing it. Are you executing any unmanaged code with your test? Unfortunately 18MB is a little too large for the contact form ... thi…

  4. NCrunch 1.x, 2.x build forever

    Sorry just one more thing I thought I'd suggest. I've noticed that you're running on the latest version of V1 (1.48), and thought it might be worth trying you out on the new beta build (V2.3). The beta build is pretty advanced now and I'd say its probably even more stable than V1. Certainly it do…

  5. NCrunch 1.x, 2.x build forever

    Thanks. The size of your solution and number of tests don't suggest anything out of the ordinary for NCrunch. Based on the fact that it does eventually build all the projects and there doesn't seem to be any specific issues showing the log file, I think this seems like purely a performance issue. …

  6. NCrunch crashes - can submit crash dmp file?

    Thanks Chris. The newest version of NCrunch V2, which was released a few hours after I responded to you above, actually has the hosted task runners removed because they were causing problems. If you're still seeing this crash, it's fairly certain that there is no relationship with unmanaged code…

  7. NCrunch crashes - can submit crash dmp file?

    Hi Chris - Unfortunately the dump file probably won't be of much use to me in narrowing down what is happening here. Have you noticed any pattern to the crash? Does it happen if you use NCrunch on another solution? Something to try is to set the [url=http://www.ncrunch.net/documentation/refe…

  8. NCrunch 1.x, 2.x build forever

    Thanks for submitting the reports. Just to clarify - the reports I'm seeing state that the solution build is extremely slow, but it does eventually seem to finish. Is this consistently what you're seeing? Or did it literally go forever in a neverending loop? Does the processing queue ever show a…

  9. TestCaseSource

    Hi, thanks for sharing the code. Something I just thought I'd check with you here is whether the .ToString() method on the Metric class returns a unique value for each Metric object. For NCrunch this is particularly important, as TestCaseSource relies on .ToString() to generate the name of each …

  10. NCrunch 2 - ArgumentOutOfRangeException Exception

    Great, thanks Ruben!

  11. Possible to hide 100%-covered nodes in statistics?

    Thanks, I'll see what I can do.

  12. Possible to hide 100%-covered nodes in statistics?

    Hi Peter - It's great to hear that your coverage is high enough for the 100% values to be getting in the way :) Before looking at implementing a specialised feature such as this, I'm wondering if I can suggest sorting the Metrics View descending by the 'Uncovered lines' column. You might find…

  13. TestCaseSource

    Hi, thanks for posting! Check that the generated tests each have a unique name. If this is found to be the case, It'd be great to learn more about how these tests are structured (and named) for me to help identify whether there are problems involved with how NCrunch is handling them. Cheers…

  14. NCrunch 2 - ArgumentOutOfRangeException Exception

    Hi Ruben - Thanks for sharing this issue. It looks to be caused by a column in the Tests Window that has somehow been set to a zero or negative size. I wasn't aware it was possible to physically do this in the UI - well done for discovering it. In theory, you should be able to get rid of thi…

  15. Distributed test failure due to api execution error

    Sadly, there may not be much else I can suggest in this case that will get this code to run on the grid node. If the API call requires the code to run as a desktop (non-service) application, the execution environment of the grid node simply cannot process it. I would recommend perhaps stubbing t…

  16. Add Pin/Unpin tests on assembly level

    Hi Jon - The grouping I'm referring to is the dropdown option at the top of the Tests Window that lets you choose how you want the tree to be structured. This is a new feature in V2, so I'm sorry for the confusion if you're not running on this version yet. The problem you're experiencing with…

  17. Distributed test failure due to api execution error

    Hi, thanks for posting. In theory, this should be as simple as updating the NCrunch Grid Node Service to allow it to interact with the desktop. After you've installed/setup the grid node, simply open up the windows services control panel and look for the service. Go to the service properties,…

  18. does not exist in the current context

    Hi, At the moment, NCrunch has no way of handling such a debug evaluation. This is because keywords such as 'await' involve the creation of whole new structures of code at a metadata level. The instrumentation that NCrunch performs on the assembly skews with the 'magic' performed by Visual St…

  19. Add Pin/Unpin tests on assembly level

    Thanks! This is helpful to know. What you've described does fit the intention of the design... I guess the only thing is that your situation does involve grouping of similar tests at higher level than fixture. When the namespace groupings were introduced in V2, the intention was to make these w…

  20. Add Pin/Unpin tests on assembly level

    Hi, thanks for this feedback. Do you might if I ask how/why you're using the pinned test status? The original idea behind pinned tests was that they would be used fairly transiently. I'm wondering if there may be a larger feature gap here. Cheers, Remco