Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. NCrunch & Visual Studio 16.5.0 - tooltips flicker

    Thanks for sharing this issue. I'm not sure at the moment how to reproduce this issue, so I guess it's question time. Did this problem appear for you suddenly after something changed? Or has it been going on for a while? Do you have the 'Optimize rendering for screen with different pixel d…

    24 Mar 2020 23:05 UTC

  2. Analysis failure for generic fixture

    Could you try the following build and let me know if this solves the problem for you? [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_4.4.0.3.msi]NCrunch_Console_4.4.0.3.msi[/url] [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_4.4.0.3.zip]NCrunch_Console_…

    23 Mar 2020 00:12 UTC

  3. NCrunch reports tests as failing even though all tests pass, and no indication why.

    Can you try setting your Log Verbosity to Detailed inside your build system, then tracing through the log to examine the execution of the failing test? It may be that the log yields information that isn't available in the TeamCity report. Could you also confirm whether the test is marked as fail…

    20 Mar 2020 23:41 UTC

  4. Analysis failure for generic fixture

    I'm having trouble reproducing the issue you've reported with this code: [code=csharp] using NUnit.Framework; [TestFixture(TypeArgs = new[] { typeof(string) })] internal class SomeFixture<TOne> { [Test] public void SomeTest() { } …

    20 Mar 2020 00:15 UTC

  5. NCrunch reports tests as failing even though all tests pass, and no indication why.

    Are you able to reproduce this failure in any form using the NCrunch VS Client? The reason I ask this is because I'm trying to establish if this is a reporting difference in the console tool itself. To my knowledge, it's not possible for a test to fail with no error information. If you can prod…

    19 Mar 2020 22:47 UTC

  6. Analysis failure for generic fixture

    Good catch, thanks for sharing this! Does changing the framework utilisation type for NUnit allow you to work around the problem?

    19 Mar 2020 10:27 UTC

  7. Unstable Test Generation

    Here's a copy/paste of an extract from a log that contains NUnit's discovery data: [12:49:18.8928-LocalAnalysisTask-43] Calling into task runner to analyse target assembly: F:\Workspaces\992\1\NUnitTestProject3\bin\Debug\netcoreapp2.2\NUnitTestProject3.dll Process 10352: 12:49:18.9112 [4] - Load…

    17 Mar 2020 23:51 UTC

  8. nCrunch.TaskRunner.DotNetCore.20.x64 Information prefix for trace output?

    Hi, thanks for posting. We don't have anything in NCrunch that integrates with NLog, and all log/trace capture is directly piped and not manipulated. My guess would be that it's using the name of the task runner process and just sticking it in the log.

    17 Mar 2020 08:40 UTC

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

    Regarding the issue you've been experiencing with the CLR exception, I'm very interested in examining this if you can isolate it. It might be related to the execution order of your code. It's possible that churn mode could surface this, as it cycles the test runners using different execution seque…

    17 Mar 2020 08:39 UTC

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

    I'll try to explain in detail how NCrunch captures these times, in the hope that a deeper understanding of this may allow the data you're examining to make more sense in its context. NCrunch captures line-level timings by measuring the wall-time of each line of code, in milliseconds (ms, 1000 in …

    17 Mar 2020 08:38 UTC

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

    It's interesting that you aren't noticing much of an improvement in the build times. 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. Probably, the mechanics of this generation is bogging down the instrumento…

    15 Mar 2020 22:51 UTC

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

    [quote=abelb;14521]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 …

    14 Mar 2020 22:19 UTC

  13. NCrunch reports tests as failing even though all tests pass, and no indication why.

    Do you have the HTML NCrunch results report for the build run? I would expect this to contain more information about any failures encountered during the run. If you try churning the tests overnight using your grid, can you produce any failure using the VS client? If there are background threa…

    13 Mar 2020 00:03 UTC

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

    Ok, I've isolated and resolved an issue where NCrunch has been corrupting x64 assemblies under optimised mode. The nature of this issue has been such that only very large assemblies have been experiencing problems. Could you try the build below to see if it resolves the problem for you? [url…

    11 Mar 2020 11:00 UTC

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

    [quote=eriove;14505]We seem to have the same error in one of our solutions. Let me know if I should try to create a smaller project that reproduces the problem as well.[/quote] Thanks for sharing this issue. Right now I have a test case that can produce the previously reported issue, and I am wo…

    09 Mar 2020 23:08 UTC

  16. Test coverage dots show wrong tests

    [quote=MatthewSteeples;14503] Where is this database is stored? If the answer is where I think it is (the NCrunch Cache Storage Path) then could having 2 different branches of the same solution (so the same sln name) open at the same time with the same path cause the issue? [/quote] In theory…

    05 Mar 2020 01:00 UTC

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

    [quote=abelb;14497]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 f…

    04 Mar 2020 23:58 UTC

  18. Test coverage dots show wrong tests

    Thanks for sending through the bug report. The report was full of internal exceptions indicating a major desync between the internal coverage database and your codebase. When these desyncs happen, they can be hard to troubleshoot as we can usually can only access the corrupted state long after e…

    04 Mar 2020 23:50 UTC

  19. Metrics page doesn't show coverage for ONE file

    Hi, thanks for sharing this problem. This doesn't look like behaviour by design. I'm thinking that it might be something caused by corruption in the coverage database, in which case a reset of the engine and rerun of your tests would have a good chance of resolving the issue. Please let me kn…

    04 Mar 2020 23:31 UTC

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

    Thanks! Yes, I think it's the package size that's triggering issues on my side. I'll update you as soon as I have more information.

    04 Mar 2020 03:23 UTC