dotCover CLI hanging

We have exactly the same problem with a new jenkins slave.

We have an old slave running fine since months, but the new slave always hangs at

Results (nunit3) saved as TestResult.xml

It doesn't make any difference if I use DotCover 2017.2 like on the old slave or upgrade to 2018.1.3.
Both slaves are running Windows10 LTSB 2016 (10.0.14393)

In the verbose log file I see the same line as @Jtsievert over an over again.

The strange thing is: If I call the exact same dotCover.exe command in the same location as the same user as Jenkins, but in a cmd.exe, it works just fine! It is stuck only for a few seconds and then finshes within some more seconds.

Hi,

Thank you for contacting us and sorry for the long silence.

Could you please provide us with more info:

• A list of all Windows updates on your PC, please refer to this how-to: https://social.technet.microsoft.com/wiki/contents/articles/4197.how-to-list-all-of-the-windows-and-software-updates-applied-to-a-computer.aspx#WMIC
• Under which user account does Jenkins build server run? In case of a limited account, you could try to use a registry-free dotCover configuration. dotCover, in this case, should be started with an additional command line parameter: /CoreInstructionSet=[x86|x64], where x86 or x64 refers to the profiled process bitness.
• Are you using Telerik Justmock on the problem agents?

This is what one of our problematic build slaves has installed:

>> Get-WmiObject -Class "win32_quickfixengineering"

Source Description HotFixID InstalledBy InstalledOn
------ ----------- -------- ----------- -----------
Update KB4049065 NT-AUTORITÄT\SYSTEM 14.03.2018 00:00:00
Update KB4054590 NT-AUTORITÄT\SYSTEM 21.06.2018 00:00:00
Update KB4089510 NT-AUTORITÄT\SYSTEM 09.04.2018 00:00:00
Update KB4093137 NT-AUTORITÄT\SYSTEM 09.05.2018 00:00:00
Update KB4132216 NT-AUTORITÄT\SYSTEM 01.06.2018 00:00:00
Security Update KB4343902 NT-AUTORITÄT\SYSTEM 30.08.2018 00:00:00
Security Update KB4343887 NT-AUTORITÄT\SYSTEM 30.08.2018 00:00:00

I'm not sure about the timing, but I believe that it worked until the April or May update and then stopped working.
After that our other slaves also stopped working one after another, without changing anything else, so it is most likely connected to one of these updates...

Our Jenkins slave runs under a normal user account without local admin rights.

We're not using Telerik JustMock. Instead we're using Moq.

Thanks for looking into it!

Hi Claudius,

Thank you for the information! Have you had time to try a registry-free dotCover configuration?

Okay, strange thing:

I activated coverage again for our build, tried the registry-free configuration and it worked. BUT: It now also worked again without the additional parameter, so the problem has vanished!
I just hope it's gone for good!

However this also means I can't help you any more in finding the original reason...

Great that it works fine for you now!
Thank you for the update, we'll keep the investigation.