robert-j-engdahl

Posts by robert-j-engdahl

1. NCrunch + NuGet PackageReference + PostSharp

   We can confirm that something fishy is going on with nuget package references on our grid nodes as well. I don't believe we use PostSharp though (that's something you need to actively configure right?). The problem seem to go away as each of our developers pull the nuget package reference into t…

   7 years ago 28 Feb 2019 12:09 UTC

2. NullReferenceException from TestPipelineManager

   Now I get [quote]Configuration setting ''NCrunch cache storage path'' was not found [/quote] After adding [quote]-'NCrunch cache storage path' C:\ncrunch\%teamcity.build.branch%\[/quote] to the NCrunch.exe invocation.

   7 years ago 02 Oct 2018 13:21 UTC

3. NullReferenceException from TestPipelineManager

   Projects that are routinely removed and readded, sure; we definitely have these. All our feature branches run on the same TeamCity, so new projects aren't created on all branches at the same time. This could make it appear as if it was removed and added again all the time. The cache file location…

   7 years ago 02 Oct 2018 12:07 UTC

4. NullReferenceException from TestPipelineManager

   So I just cleared the cache but now the following error is back: [quote] Object reference not set to an instance of an object. - System.NullReferenceException: Object reference not set to an instance of an object. at nCrunch.Client.TestPipeline.TestPipelineManager. (IEnumerable`1 ) at nCrunch…

   7 years ago 02 Oct 2018 11:13 UTC

5. NullReferenceException from TestPipelineManager

   Our TeamCity (which uses distributed NCrunch for testing) occationally fail with errors similar to the following: [quote]Object reference not set to an instance of an object. - System.NullReferenceException: Object reference not set to an instance of an object. at nCrunch.Client.TestPipeline.Tes…

   7 years ago 02 Oct 2018 10:05 UTC

6. TeamCity distributed NCrunch is very slow

   That sounds awesome. Flying blind is not fun. I'd like to see some measurement of the communication overhead and how much time is spend waiting for NCrunch nodes to become ready. A lot of different software is involved in this setup, so a trouble shooting guide would also be quite nice (but then…

   8 years ago 06 Jun 2018 11:06 UTC

7. TeamCity distributed NCrunch is very slow

   Ok, That is consistent with the results I can measure. Then I'd like to make a feature-request for a default-batch-size option, because I fear there is a huge overhead in the batch communication. I still think the distributed NCrunch builds are insanely unstable in terms of build-times, compa…

   8 years ago 06 Jun 2018 09:30 UTC

8. TeamCity distributed NCrunch is very slow

   It appears the AtomicAttribute can be applied to assemblies as well. So it would be relatively easy for us to test if that improves speed (there are still 72 of them, so there is something to be parallelized). I'll keep you posted on how that goes. If that works wonders, I would suggest a defau…

   8 years ago 05 Jun 2018 09:23 UTC

9. TeamCity distributed NCrunch is very slow

   I remembered wrongly. The clean-up notifications are like [Core-20] Cleaning up workspace: C:\Users\administrator.ACCU\AppData\Local\NCrunch\3748\25 and they amount to 20'ish seconds. We only see them when ncrunch is configured to also build and test on the TeamCity server. I expect the nod…

   8 years ago 05 Jun 2018 06:17 UTC

10. TeamCity distributed NCrunch is very slow

    I can't tell if this is a regression. We just tried out NCrunch with TeamCity to see if it would work. We are flying blind here. I understand the diagnostic message will go away with the next upgrade. We look forward to it, and there might have been a minor release since we upgraded the server…

    8 years ago 05 Jun 2018 05:49 UTC

11. TeamCity distributed NCrunch is very slow

    We went from PowerShell xunit console invocation on 8 cores @ 8 minutes to NCrunch grid with three nodes each with 18 assigned cores @ 7 minutes to 22 minutes, depending on the load. Our log is full of entries like [GridMessageSender-113] Resetting ping but they don't need to have anything…

    8 years ago 04 Jun 2018 13:31 UTC

12. Framework Utilisation Types missing Xunit v2+

    Things being as they are, perhaps the error message could list the location of the violating test code? Right now I get a warning pr assembly. On a side note: I think it is reasonable that if performance can be increased at the cost of random test parameters, that is acceptable. We don't use ra…

    9 years ago 24 Jul 2017 21:31 UTC

13. Framework Utilisation Types missing Xunit v2+

    The download count of the nuget AutoFixture.Xunit is significant. Perhaps it would be fair to detect uses of AutoData and AutoInlineData and give a friendly warning so that others will know that these guys are obsolete.

    9 years ago 13 Jun 2017 09:13 UTC