Closed AndrewGretton closed 6 years ago
@AndrewGretton please upgrade to latest version agent, this is a known issue that we fixed. https://github.com/Microsoft/vsts-agent/pull/1407 https://github.com/Microsoft/vsts-agent/releases/tag/v2.131.0
Thanks @TingluoHuang, this has resolved the issue.
Agent version and platform
Agent version 2.129.0, running on Windows Server 2016 v1607, using VSTS (the agent path says "d:\tfsagent" but we have now fully migrated to VSTS)
What's not working?
I have installed 2 agents on a single machine. I am running a CI msbuild script which performs compilation of around 50 .NET projects, using the /m flag, and then runs nunit tests. When only one agent is enabled on the machine, the build runs reliably. When the second agent is enabled, the build on both agents usually fails, if both agents are running a build at the same time.
This same msbuild job has been running under Teamcity for several years, concurrently on the same agent, with no concurrency-related failures.
The failure message is emitted into the log at different places, it's not always the same place. For example, we have observed it happening 1 minute into the build and also 9 minutes into the build. The error reported in the build results is:
Agent and Worker's diag log
I have pulled what I believe to be the relevant section from the agent's diagnostic log but I can attach the whole thing if need be. I want to note that the AD user which runs builds, is a member of the local administrators group on the build machine.
My question
How can I fix this so I can reliably run multiple agents on the same machine?
Thank you!