Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Setting instrumentation mode to Optimised fails to take project references in account

    [quote=abelb;14492]I tried the submit form twice, once with a RAR attachment and once with a ZIP attachment, but in both cases I received a 404 error. Size of upload is 25MB (rar) or 29MB (zip).[/quote] Can you try emailing it directly? support at ncrunch.net.

    04 Mar 2020 03:06 UTC

  2. Setting instrumentation mode to Optimised fails to take project references in account

    [quote=abelb;14490]PPS: is there a trivial way to find the output DLL location? There is a myriad of directories and I struggle with finding precisely the one that belongs to the current (failing) build cycle of NCrunch. "Execution steps" is empty, and "processing queue" doesn't seem to give details…

    04 Mar 2020 02:59 UTC

  3. Setting instrumentation mode to Optimised fails to take project references in account

    [quote=abelb;14487] I understand. Do you need the source code, or does testing the instrumentation bug only require the compiled DLL? I can easily send either to you. Bringing it down to a small sample will be hard, though, after compilation this is currently 5+MB for the X.Common.dll alone. And al…

    04 Mar 2020 01:25 UTC

  4. Setting instrumentation mode to Optimised fails to take project references in account

    Nice investigation work! The problem here would be that the code in your X.Common project is causing the compiler to emit a structure that we're not handling right during the optimised instrumentation. We're then corrupting the assembly and the runtime loader can't read it. It's possible to use…

    03 Mar 2020 23:09 UTC

  5. Tests not distributed evenly across grid nodes

    The key variable here is the time the overall fixture takes to run excluding the time spent executing each child test. If the execution time of the fixture is too high, all of its child tests will be grouped together in the same test execution task so that the runner doesn't need to make the expens…

    03 Mar 2020 23:01 UTC

  6. Reallocating NCrunch License

    Hi, thanks for posting. It should be possible to simply provide the existing licence code to the new developer. They can enter in into the software and all should be well. Don't forget to also remove the licence code from the previous developer's machine.

    03 Mar 2020 02:54 UTC

  7. Tests not distributed evenly across grid nodes

    Thanks for posting. Looking at the timeline report, my best guess is that this is being caused by the batching of tests. In this instance, we have 5 nodes but only 3 test tasks, so two nodes are left without a task. Do these tests have any long running code in a fixture setup routine, or are th…

    02 Mar 2020 23:27 UTC

  8. Risk/Progress bar not remembering width.

    We'd like to fix this, but presently we don't know what's causing it. We can't seem to reproduce it. If you have any ideas on what might be triggering it, we'd love to hear them. Are any of your other NCrunch tool windows affected in the same way?

    29 Feb 2020 03:11 UTC

  9. exception running tests on the grid

    [quote=samholder;14473]I'll try and do this but not super easy as lots of machines to update, and happens infrequently. Will this speculative fix be included in the main NCrunch release? It might be easier to schedule the update at some later date with a released version[/quote] Yes. We have som…

    27 Feb 2020 21:56 UTC

  10. Unstable Test Generation

    I recommend setting your Log Verbosity to detailed, then examining and comparing the trace logs that can be extracted from the discovery and test execution tasks inside the processing queue. When NCrunch reports this issue, it does so by comparing test counts. So it will discover all the tests…

    25 Feb 2020 08:37 UTC

  11. Unstable Test Generation

    [quote=ericschmidt;14468]You listed TestCaseSource, ValueSource or DataPointSource, but could using regular TestCase also lead to this? I am currently writing tests for a parser object and started getting this error as well but I'm only using the TestCase attribute and there's no dynamic generation …

    24 Feb 2020 22:56 UTC

  12. ExclusivelyUses functionality when building

    Is there perhaps an option to include the tool inside your project space so it gets copied to the workspace and doesn't clash with itself? Sorry I'm just trying to help fish for ideas.

    21 Feb 2020 23:12 UTC

  13. Project Incorrectly Identified As Test Project.

    Thanks for posting! I'm glad you like NCrunch! NCrunch identifies test projects by their assembly references. For example, if your project has a reference to NUnit.Framework, it will be considered an NUnit test project. If you disable the appropriate test framework in the project settings un…

    21 Feb 2020 23:10 UTC

  14. ExclusivelyUses functionality when building

    We don't presently have any feature in NCrunch that allows you to manage the concurrency of the project build or analysis tasks. Generally when this sort of problem appears the approach we usually take is to try and find a way to fix the build so that concurrency is not an issue. How critical is…

    21 Feb 2020 23:05 UTC

  15. Uwp library: This assembly is built by a runtime newer than the currently loaded runtime and cannot

    Sorry, we don't support UWP projects - [url=https://www.ncrunch.net/support/frameworks]https://www.ncrunch.net/support/frameworks[/url] The closest we came to this was the old support we had for Windows Store Apps many years ago. This was pulled out after it became impossible to maintain. I don…

    21 Feb 2020 22:46 UTC

  16. NCrunch.Framework 4.0.0.1 missing reference to Framework dll?

    Hi, thanks for sharing this issue. I can't seem to reproduce this on my side... 4.0.0.1 with .NET Core 3.1 seems to both reference and compile ok. Is there any chance you could send us a test solution that can reproduce this?

    20 Feb 2020 23:11 UTC

  17. Cannot build on Grid Node with dotnet core 3.1 project

    Hi, thanks for sharing this issue. The error that you are receiving is caused by the primary build target referenced by the .proj file not being present in its expected location. Probably, the issue here is some kind of inconsistency in the toolset being used between the grid node server and you…

    19 Feb 2020 22:27 UTC

  18. Troubleshooting build of non-SDK style project using PackageReference

    Thanks for providing the extra detail. It looks to me like you're encountering this issue: [url=https://forum.ncrunch.net/yaf_postst2498_-NET-Core-2-0-Support-with-re-located-build-folder.aspx]https://forum.ncrunch.net/yaf_postst2498_-NET-Core-2-0-Support-with-re-located-build-folder.aspx[/url] …

    14 Feb 2020 23:08 UTC

  19. Post Build Event exitcode 3

    Hi Dirk, Thanks for sharing this issue. The 'Run post-build events' configuration setting can be a little misleading, and we've recently updated the documentation to reflect this. Basically, this setting only control build events that are specified using the MSBuild Properties. It will not s…

    13 Feb 2020 22:17 UTC

  20. Troubleshooting build of non-SDK style project using PackageReference

    Hi Kaleb, Thanks for sharing this issue in such detail. NCrunch should normally detect the project.assets.json file (along with its related 'obj' files) and copy this into the workspace with some minor manipulation. How are your projects structured in regards to project.assets.json? Is the f…

    13 Feb 2020 22:12 UTC