Forum member

MarcChu

29 posts

Posts by MarcChu

  1. Console Runner On A CI Server, Optimization Hints

    Okay, I am now passing -EnableRDI false on my command line, and it has greatly decreased processing time, down to about 15 minutes. However, in closer examination of resource usage on my distributed node, I can see that it is still writing RDI information on that machine, after the engine shuts down…

  2. Console Runner On A CI Server, Optimization Hints

    I've started using the Console tool to run tests on my CI server. I'm running tests on the build server, as well as one distributed node, so about 35-40 threads. Currently, I'm running about 4000 tests, the vast majority of which are unit tests. At present, it may take 60-80 minutes to run my en…

  3. Console Runner, OpenCover and NUnit reports w/ SonarQube

    Okay! I installed the new Console version on my build server, and the new Grid Node Server versions. I've only had a single build run so far. As noted above, changing DebugType to portable had already gotten rid of the duplicate <File/> elements. But I can also see that the OpenCover report di…

  4. Console Runner, OpenCover and NUnit reports w/ SonarQube

    [quote]It would be interesting to see if switching to a portable PDB on your side would solve this particular problem - I think there is a high probability that it will.[/quote] Yes, it does look like portable PDB's fixed that issue. Thanks. [quote].. do you by chance have a non-NCrunch OpenCover …

  5. Console Runner, OpenCover and NUnit reports w/ SonarQube

    [quote]The data in the Tests Window is shown according to the first node that was able to build the project. To see the other build results, you can use the Processing Queue Window, which reports on all build activity from across the grid. To get more detailed build results in this window, you'll ne…

  6. Console Runner, OpenCover and NUnit reports w/ SonarQube

    Yes, I see the complications. NUnit seems to have been overtaken over the years by XUnit, and OpenCover is an archived project altogether. Unfortunately, we're pretty wedded to the former. As to the latter, since we're still on .Net Framework 4.8, this is the only thing that I could get (so far) to …

  7. Console Runner, OpenCover and NUnit reports w/ SonarQube

    I have a solution with many .Net Framework 4.8 projects. I've been working on CI/CD automation, using Jenkins pipelines. I have a large suite of NUnit tests that I run, and am attempting to collect test and code coverage results, which I then pass to SonarQube for analysis/tracking, as well as Jenki…

  8. Why won't tests run on distributed node?

    Yes! That seems to have improved things greatly. It will take some time to determine whether this looks well solved, but I'm definitely optimistic, given the initial results. Also, I initially [i]thought[/i] there might still be a problem with re-running fast-failing tests all being directed to a…

  9. Why won't tests run on distributed node?

    I can export the NCrunch Tests window for you. But it appears that there is never any difference between the "Last Execution Time" and "Expected Execution Time" for any individual test. Also, I never see any execution times for fixtures on this window that seem to make any sense. I would expect them…

  10. Why won't tests run on distributed node?

    I'm using NUnit 3.13.2. I can confirm that the tests that seem to cause the biggest problems don't have very expensive setup (relative to other tests that run fine). Actually, I just did a test run (they ran automatically as they were impacted by code changes). Three different fixtures ran, as th…

  11. Why won't tests run on distributed node?

    OOOOH, hm, it seems that I've identified a use case where this happens: if an entire test fixture fails for some reason (in this case static setup for the test fixture), then every individual test in the fixture will fail very quickly. Upon the next attempt to run those failing tests, they'll all be…

  12. Why won't tests run on distributed node?

    I'm not seeing any big differences in expected vs. actual execution times. But if I'm reading you correctly, then this could be working as intended if my fixture simply has a LOT of fast executing tests. Can you quantify "very low execution times" for me? As an example, I had one task run 286 te…

  13. Why won't tests run on distributed node?

    Okay, yes, it seems that the test projects in question were themselves depending on test projects that had Required Capabilities defined. Now that I've refactored to get rid of those dependencies, the tests are building and running as expected. Thank you. I do have another issue that's somewhat…

  14. Why won't tests run on distributed node?

    Well, all of my nodes have been able to run [b]some[/b] subset of the tests. So, while I haven't yet done a new project from a template to test this specific thing, have little reason to doubt that those tests would successfully build and run. The problem I'm having is with only a select few test…

  15. Why won't tests run on distributed node?

    I'm trying to determine why certain projects won't run on my distributed grid nodes. I have certain test projects that will build and run just fine on my local machine. However, in the NCrunch Processing Queue window, these projects will always display as "Pending" for any other server, for both …

  16. Apphost.exe was not found

    An interesting new revelation is that the one working grid node server now no longer builds after a restart. All grid nodes have Visual Studio Build Tools 2022 Preview installed, 17.0.0 Preview 2.1. They also all have SDK 6.0.100-preview.6.21355.2 installed, and at least 5.0.302 and 5.0.101 also.…

  17. Apphost.exe was not found

    I'm having this same problem. However, I'm having it in VS2022 preview (it seems that others are having it in VS2019), and I'm not having the problem locally. Rather, I'm having the problem on 2 out of 3 of my distributed nodes (the other one builds just fine). When I first ran into this problem, I …

  18. Frequent FileLoadException when running tests that call into modified assembly

    Sorry for the delay in responding to this. Yes, we definitely do auto-increment our versions on build. I didn't try disabling this, as it's done through an AssemblyVersionAttribute in a shared AssemblyInfo.cs, and would affect every project in our solution. And I doubt this is the sort of scenar…

  19. Frequent FileLoadException when running tests that call into modified assembly

    We have a large solution, and one particular project that seems to cause problems. This project ("Woti.Xift.Core") contains many common types, and so is taken as a dependency (directly or indirectly) by most other projects in the solution. It seems that whenever this project is modified, the tests…

  20. Insight on what qualifies as an "Impacted" test

    I've got a solution with DOZENS of projects and hundreds of tests. This solution is so large that I don't expect to get any kind of specific answer as to what's causing my problem, so I'm just looking for some insight: how does NCrunch determine when a test is 'impacted'. I have found that the…