Forum member

abelb

155 posts

Posts by abelb

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

    Found the culprit. My X.Common.dll becomes an invalid DLL after instrumentation is added. I'd like to help to get to the bottom of this, as it is clearly caused by the new instrumentation algorithm(s). The line in the log file that hinted at this was: [quote]Resolved file has a bad image, no meta…

    03 Mar 2020 18:32 UTC

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

    [i](I submitted this bug through the Submit Bug button in NCrunch, but I cannot find it back here, hence this copy, so that I can open the discussion ;)[/i] I was eager to try the new instrumentation mode, esp. for its performance speed up (I have a large project and just the msbuild phase takes …

    03 Mar 2020 16:49 UTC

  3. Failing tests are not run with higher priority

    Thanks for your response. This is NUnit 3.6. Running it from NUnit's test runner, it runs all tests in approx. 3 minutes. This test runner runs them synchronously. Looking at the failing tests, most run in 3-5ms it seems. Only a handful of tests seem to have a genuinely slow execution speed (above 1…

    16 Nov 2017 18:17 UTC

  4. Failing tests are not run with higher priority

    I seem to recall that NCrunch favors failing tests, understandably, because the programmer would want to know whether a fix will have had impact on such failing tests. However, I notice that, at least when there are a lot of failing tests, this doesn't happen. For instance, all successful tests a…

    15 Nov 2017 22:56 UTC

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

    This seems to have solved at least some of the problems mentioned earlier in this thread: http://forum.ncrunch.net/yaf_postsm11442_Async-build-and-build-in-general-is-a-lot-slower-on-VS-2017-Preview-4.aspx. Thanks!

    03 Nov 2017 17:29 UTC

  6. Async build and build in general is a lot slower on VS 2017 Preview 4

    Hi Remco, it looks like your excellent fixes in that other issue (http://forum.ncrunch.net/yaf_postsm11410_NCrunch-does-not-honor-the-max-timeout-and-runs-tests-forever.aspx) also fixed this. I had some time today to run some performance tests. The main project that caused me to write this bug re…

    03 Nov 2017 17:28 UTC

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

    Such an extension to the algorithm would be great, but I'd gather, also rather complex. A much simpler improvement that would already reap many benefits, would be something along the following lines: [list][*]Take the set of X of all fast tests (i.e, that are eligible for fast-lane processing…

    24 Oct 2017 12:06 UTC

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

    [quote]I noticed that after several runs, the memory usages increased and stood around 3.5GB for the highest test runner. Not sure what happened there.[/quote] Actually, I can see this happening now, with the FSharp tests (set of 4196 tests). 1st run: slow, but no issue, 2nd run, fast, split over 4…

    23 Oct 2017 20:49 UTC

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

    It turned out that the MSI installer [i]removed[/i] the installation properly, but [i]did not install[/i] anything in the unnamed default VS installation. It seems to me that there are quite a few confusing scenarios possible with the new side-by-side possibilities of Visual Studio 2017. Manually…

    23 Oct 2017 20:30 UTC

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

    I've tried installing using the MSI, but that gave me the following error after starting VS 2017 again (in a messagebox): [code=plain]--------------------------- Microsoft Visual Studio --------------------------- The 'nCrunch.VSIntegration2010.CrunchPackage, nCrunch.VSIntegration2017, Versio…

    23 Oct 2017 16:15 UTC

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

    While this was after a restart, it was also after an update of VS 2017 Preview 15.5 P1. After a new restart, everything went fine again, probably a one-time issue.

    21 Oct 2017 17:24 UTC

  12. Manual install instructions should probably be renewed a bit

    Just some findings of going over the manual installation instructions again today: There seem to be a few slightly confusing statements in the manual install instructions ((- BROKEN LINK -) [quote]If in future you choose to upgrade to a new version via installer or a newer zip package, make su…

    20 Oct 2017 13:20 UTC

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

    Thanks for the quick update, I understand this can take time. So I tried installing the MSI for 2017 that you linked earlier (http://downloads.ncrunch.net/NCrunch_VS2017_3.12.0.3.msi), but it gives me an "another installation is already in progress". Possibly this is caused by me having three in…

    20 Oct 2017 13:06 UTC

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

    [quote] I also recommend using an x64 test process for this project.[/quote] Yes, but as this thread has shown, I have tested with both x64 and x86 processes. Ideally, this project is tested on both x64 and x86 (some tests have specific bitness) but that can be covered on the build server. The thin…

    20 Oct 2017 10:17 UTC

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

    Hi Remco, many thanks for this. I will be away for a week, not sure I can test this before that, but performance improvements of 1000% is [b]BRILLANT[/b] (they should have a Nobel prize for that!). The "intermittent" situation happens always on the FSharp open source project. This project also c…

    09 Oct 2017 15:22 UTC

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

    I can imagine it is tricky to research. Today I tried to repro again with the project I sent you and for some reason I couldn't, even after numerous tries. What I did notice, though, is that even empty tests run very long, between 35 and 1800ms, which is rather odd. I have many tests in other pr…

    05 Oct 2017 16:37 UTC

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

    I've send you a repro through the contact form. I had to try several times, with my original repro (which fails 100% of the time) I couldn't get through, it gave me a 404 error after submitting (I think because the zip was too large, some 25MB). The current repro does not always successfully rep…

    04 Oct 2017 18:49 UTC

  18. Installing NCrunch on nicknamed multiple installations of Visual Studio 2017

    In case you're considering this at some point in time, I have asked Microsoft to update vswhere to be able to enumerate by nickname. Not sure it helps with MSI installations, but here it is just in case: https://github.com/Microsoft/vswhere/issues/104 (it is done/resolved, but only as specific build…

    03 Oct 2017 16:04 UTC

  19. Installing NCrunch on nicknamed multiple installations of Visual Studio 2017

    Thanks. I didn't see that feature request (I searched for "nickname"). I don't think it is impossible with MSI, but you'll probably need customized actions. This post (https://developercommunity.visualstudio.com/solutions/21956/view.html) explains that any VS2017 gets a directory in [code]C:\Progr…

    28 Sep 2017 13:15 UTC

  20. Installing NCrunch on nicknamed multiple installations of Visual Studio 2017

    Visual Studio 2017 supports side-by-side installation of multiple versions. Very handy, but I am wondering how / whether this is supported by NCrunch. Am I entitled by my license to install it on a single computer to each instance (nickname) of Visual Studio, or do I need separate licenses? And, …

    27 Sep 2017 18:07 UTC