Forum member
MatthewSteeples
147 posts
Posts by MatthewSteeples
-
Intermittent errors on single grid node
We have 2 identical grid nodes configured. Occasionally one of them will display this error (but not for everyone using it). A restart of the node or the client usually resolves it. The project in question is a single NETSTANDARD library in a solution full of .NET 4.7.2 projects. It doesn't depen…
02 Sep 2019 11:29 UTC
-
Exception using Grid Nodes (after Update to 3.29.0.7)
This error keeps coming back for us. 3.30.0.1 is the version on the client and the grid node
02 Sep 2019 11:18 UTC
-
Grid Node - AccessViolationException - Protected Memory Issue
That seemed to work for us for a while, but we're getting an error where we wouldn't expect now (and it doesn't happen all of the time, only intermittently - a restart solves it for a while) [code=csharp]NCrunch: This test was executed on server 'THREEOAKS' System.TypeInitializationException: …
22 Aug 2019 14:58 UTC
-
serious typing lag when running NCrunch in VS2019
Can definitely recommend the distributed processing. Our lower powered devices have local processing disabled and rely solely on grid nodes. Remco: Is it possible to disable the affinity options (is it as simple as putting all of my cores in both options)? As you've configured the processes prope…
22 Aug 2019 10:41 UTC
-
serious typing lag when running NCrunch in VS2019
[quote=offset123;13702] - CPU usage while slashing: the process with highest usage is devenv, but it only uses 5-7%. Everything else is 1% or below. System idle is around 84-87% [/quote] How many "logical processors" do you have on the computer? With multi-processors being common, the percentag…
07 Aug 2019 13:38 UTC
-
serious typing lag when running NCrunch in VS2019
I've noticed it here too. NCrunch 3.29, VS 2019 16.2.1, Win 10 Pro 1903 / 18362.267 CPU usage of devenv does seem to spike when typing. Disabling NCrunch (from NCrunch's menu) appears to fix this
07 Aug 2019 13:36 UTC
-
Exception using Grid Nodes (after Update to 3.29.0.7)
I (another user) encountered this too. Are you sure you've updated your VS Plugin to 3.29 too? That's what caused it for me
07 Aug 2019 13:27 UTC
-
InvalidCastException installing Grid Node 3.29
Changed the default path in the wizard to the D drive. Still plenty of space. Looks like the path information was saved (when I go into settings afterwards) and the service works fine if you cancel out of the wizard, but thought you'd want to know. [quote]See the end of this message for details o…
07 Aug 2019 12:09 UTC
-
xunit issue
Thanks for the thorough explanation. We try to keep our platforms aligned but some developers are a bit more lax at running updates than others, and being a remote team I can't stand over their shoulders to make sure it's done :P
06 Aug 2019 15:24 UTC
-
xunit issue
Not sure what I did wrong with the first url. Try this one - https://ledgerscope-my.sharepoint.com/:i:/p/matthew/EZ3R8UMzMJVOuGX_1sF69iMBvUsSkeC043DaJXsyr5aJBA?e=jhrRw0 We've since updated VS to 16.2 and it appears to be working fine now, so it's no longer an issue but may help someone else if th…
05 Aug 2019 13:11 UTC
-
xunit issue
First thing this morning one of our developers was unable to get the project to build via NCrunch with the following error message: [quote]..\..\packages\Microsoft.Net.Compilers.3.2.0\tools\Microsoft.CSharp.Core.targets (100, 10): The "Nullable" parameter is not supported by the "Csc" task. Verif…
05 Aug 2019 09:40 UTC
-
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
It was via InTune. [url=https://ledgerscope-my.sharepoint.com/:u:/p/matthew/EShVdtrn4OlJkJkIuGL4gWkBz5aoIFV93bEqoVFphCOpOA?e=0Jvrhc]This is the log[/url] from running it on the command line (looks similar). Sorry for being a pain!
02 May 2019 07:48 UTC
-
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
Nothing is showing in add/remove programs, and C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions has no files or folders containing ncrunch in it.
02 May 2019 07:40 UTC
-
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
Have given that one a try and we got a bit further. It identified where VS was installed but still failed on the install. Logs are [url=https://ledgerscope-my.sharepoint.com/:u:/p/matthew/EVi8qQJanglCsnTMeqrZs68BssCti22Br22HS8Qm4SvmgA?e=2fL9fT]here[/url]
02 May 2019 07:31 UTC
-
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
[quote=michaelkroes;13433]We’ve had a closer look at this in the code. We’ve prioritized a task for the coming release where we are going to try and tackle this. [/quote] That's great. You know where we are if you'd like a tester :)
29 Apr 2019 13:53 UTC
-
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
Yes that was run from InTune. It runs installers in "unattended" mode, so there's no UI to speak of. I'm assuming there isn't anything you can change from your side to make the checks run not in the UI?
28 Apr 2019 15:52 UTC
-
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
We've definitely reached the limit of my understanding of how MSI works, but it would appear that InTune wants to install it in "Server" (headless or quiet) mode, but the checks are done in "Client" mode so are skipped. Does that mean anything to you?
25 Apr 2019 12:59 UTC
-
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
I'm unable to uninstall the 2017 version as I no longer have 2017 installed, but I suspect that it's still some InTune jiggery pokery going on. When loading the MSI, it then insists that it's going to install it from a copy that it's keeping in C:\Users\MatthewSteeples\AppData\Local\mdm. The log…
25 Apr 2019 11:59 UTC
-
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
I have a 3.23.10 installed for 2017, and a 3.25.2 installed for 2019. I don't actually have 2017 installed any more so I'm going to try and remove both of them
25 Apr 2019 11:28 UTC
-
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
Sorry, I should have been clearer. This was me running the MSI from the command prompt and it still fails with the same error message (just after the 11:52:48:488 timestamp)
25 Apr 2019 11:06 UTC