abelb

Posts by abelb

1. Installing NCrunch with Multi Vs2019 instances?

   [quote]With the range of instances you have installed, manual installation is probably a better option anyway. It will give you more control over which instances are targeted.[/quote] Thanks, makes sense. Didn't see your answer before today, strange. I'm not really happy with all the VS IDE ins…

   6 years ago 21 May 2020 12:25 UTC

2. Installing NCrunch with Multi Vs2019 instances?

   @Remco, thanks for the insight, I didn't know of the limit of 3 instances. [quote]under normal circumstances we should be able to handle up to 3 instances with the MSI[/quote] What is the definition of "instance"? If I open up the VS2019 installer, it shows 3x VS2019 (Community, Pro and Enterpri…

   6 years ago 22 Apr 2020 10:08 UTC

3. Installing NCrunch with Multi Vs2019 instances?

   Only way I could get it solved was by installing it manually (which is really a very simple process of copying some files, I should've thought of that sooner ;). @Remco, if you'd like to investigate let me know, the scenario is (so far) reproducible. Maybe the scenario (installing a new VS instan…

   6 years ago 21 Apr 2020 22:30 UTC

4. Installing NCrunch with Multi Vs2019 instances?

   @GreenMoose, thanks. I tried it, but unfortunately, that option /u doesn't work with the MSI and NCrunch doesn't come with an EXE anymore (or at least I can't find it). I get a popup for msiexec, which shows a lot of options, including /u (repairs all required user-specific registry entries), but th…

   6 years ago 21 Apr 2020 19:58 UTC

5. Installing NCrunch with Multi Vs2019 instances?

   Hi Remco, Michael, I assume it was resolved through the mail exchange, but I'm currently running in the exact same scenario (just installed VS Community side-by-side after previously having installed VS 2019 Pro and Enterprise). I can't seem to get NCrunch to work in the new installation. I tried…

   6 years ago 21 Apr 2020 18:36 UTC

6. Failing tests are not run with higher priority

   Totally forgot about this thread, but I think that presently, the test prioritization works as expected. I did notice the "bucketing system", where it kind-of depends how many tests (incl. failing tests) end up in the same task or bucket. The Processing Queue shows this properly. My modus-operand…

   6 years ago 30 Mar 2020 14:35 UTC

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

   I've meanwhile tried to isolate it a few times, but can't (yet) find a continuously reproducible way. Somehow it seems to matter whether I do a full reset with certain settings or not (i.e., with one set of settings, it raises the CLR exception always, with another it still raises, until I do a full…

   6 years ago 30 Mar 2020 13:23 UTC

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

   Interestingly, when I set the instrumentation settings courser, only on the outer projects, the timings are even more off, with the top method being close to 800.000ms, and total running time down to 5s (in itself logical, because there's now less overhead, in fact, without any overhead, it runs in …

   6 years ago 16 Mar 2020 13:52 UTC

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

   (edited), the line-level timings are shown in ms, and I understand that they don't add up (they are cumulative for the line and everything after), but that would mean that the largest timing should be the entry point, and that it ought to be somewhat similar to the total execution time of the whole …

   6 years ago 16 Mar 2020 12:10 UTC

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

    [quote] It's possible that this is due to the nature of FSharp. I've noticed that FSharp assemblies seem to have a huge amount of generated code. [/quote] This is correct. Any let-bound function in a module, nested, curried becomes an auto-generated class that essentially captures the closure as it…

    6 years ago 16 Mar 2020 12:04 UTC

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

    And another thing: when I remove instrumentation of half of the projects and do a full rebuild of the whole solution, I get the [b]System.InvalidProgramException : Common Language Runtime detected an invalid program.[/b] back. Still researching that one. It happens in a tail-recursive [b]rec[/b] fun…

    6 years ago 15 Mar 2020 11:25 UTC

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

    [quote]The new instrumentation system shouldn't have much effect on the actual running times of your tests ... but builds and discovery will be much faster :)[/quote] Yes, I read that in your extensive blog post as well. I did some timings, and it seems that the build times, at least for those l…

    6 years ago 15 Mar 2020 11:24 UTC

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

    Great work! A few hours of testing, and trying every solution that has NCrunch-enabled tests all seem to work, they now report exactly the same number of tests and the same ratio failed vs success as when using the Legacy mode, and so far, between the failed tests, I haven't seen [b]ExecutionEngineE…

    6 years ago 14 Mar 2020 16:24 UTC

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

    [quote]The nature of this issue has been such that only very large assemblies have been experiencing problems.[/quote] That explains why the issue was not visible once I tried to create a smaller repro. Thanks! Must've been a trick one! I will try the build, probably today, once I'm behind my de…

    6 years ago 13 Mar 2020 13:23 UTC

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

    Just found that there are more issues down the line, causing sometimes "Recorded exception Common Language Runtime detected an invalid program.". Though in this case, it happens in a specific spot. I tried to create a new empty project with only the offending function(s), but so far, that just runs …

    6 years ago 04 Mar 2020 14:45 UTC

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

    Yep. They're on their way. I needed to split it, and use 7-zip to get it down a notch further, apparently, my or your server doesn't like attachments above 20MB. The second one contains the NuGet packages, use them as-is, because an unguarded nuget restore will wreck the fsproj/csproj files (if you …

    6 years ago 04 Mar 2020 03:19 UTC

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

    I tried the submit form twice, once with a RAR attachment and once with a ZIP attachment, [h]but in both cases I received a 404 error[/h]. Size of upload is 25MB (rar) or 29MB (zip). [quote] Choose Advanced->Browse to workspace[/quote] duh, I knew that! Must've been tired or something missing it…

    6 years ago 04 Mar 2020 03:03 UTC

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

    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. I found it previo…

    6 years ago 04 Mar 2020 01:45 UTC

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

    PS: I found other issues with the "optimised instrumentation" as well, that warrant more investigation: that particular project had ~470 tests failing in TeamCity and NCrunch with Legacy mode, but 515 failing with Optimised mode. These differences are troubling, though it shouldn't be too hard to fi…

    6 years ago 04 Mar 2020 01:41 UTC

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

    > Since a recent VS update, we've noticed PEVerify seems to fail on assemblies produced by the FSharp compiler. Correct, but this DLL, when compiled normally, creates PE-verifiable IL code. > It's likely this is a known problem within MS by now. Yes, it is. Indeed, there are quite a few r…

    6 years ago 04 Mar 2020 01:20 UTC