No Compatible Agents

Hi All!

I've encountered a problem and would like your assistance.

Clean install of TeamCity 7, TFS project established and connected sucessfully, but whenever a build is triggered (auto or manual), it sits in the queue. When I view the Build Configuration, it says I have 2 compatible agents (local, and additional box for testing purposes). Both agents have the full compliment of build runners. However the Build Queue's Time to Start tooltip says, "This build will not start because there are no compatible agents which can run it". This doesn't make sense as there are 2 agents properly configured, both of which say they're compatible.

Please assist.

Thanks,
-Matt

8 comments
Comment actions Permalink

Hi Matt

Please open build configuration settings on tab #8 - agent requirements.
Do you sse any unmet requirements there?

0
Comment actions Permalink

Thanks for the reply, Michael.

Tab #8 - Agent Requirements - both of my agents are listed under "Compatible agents" The only requirements I have for Agents are DotNetFramework4.0_x8, system.os.name contains Windows. Then for Build runner requirements I have DotNetFramework4.0_x64 and Exists=>DotNetFramework3.5.*

Is there anything specific I need to require for my build agents?

Thanks,
-Matt

Message was edited by: Matt Dufek - Added extract of logs and screenshots of the agent compatibility



Attachment(s):
teamcity_agent_logs_2012-04-19.zip
Images.docx
0
Comment actions Permalink

I am having this problem also, but with TeamCity 8.0.4.  It doesn't happen with all my build configurations, but it happens consistently with a couple of them.  A build is queued, but reporting "???" as "Time to Start" and "No agents" for "Can run on".  Clicking into it shows more: "Cannot estimate this build.  There are no agents suitable for this build and builds depending on it."
queued.png
queuedoverview.png

However, clicking on the "Compatible Agents" tab shows one compatible agent.  There are no dependencies.  As far as I can tell, nothing should be blocking this build from starting.
agents.png

Eventually, the build does start on its own.  Each queued run varies in time to start, but it always does eventually run.

0
Comment actions Permalink

Hi,

Do you use snapshot dependencies with "Run on the same agent" option? Message like this: "There are no agents suitable for this build and builds depending on it" means both builds combined by snapshot dependency with run on the same agent share NO agents in common.

0
Comment actions Permalink

A number of my builds do use Snapshot Dependencies but only some have the "Run on the same agent" option.  Also, the builds that are coupled with that "same agent" option have identitcal requirements.  I never imposed any agent requirements; there's just a couple of build runner requirements ("DotNetFramework4.0_x86 exists, for example) which are satisfiable by all my agents.  The screenshots in my previous post were from a build that has no dependencies, but other builds have dependencies on it.

Even if it were the case that there was some invisible requirement that was blocking my build, I wouldn't expect to see the builds get unstuck on their own after some amount of idle time.  The duration varies for each queued run, but the builds will eventually go through anywhere from 60 seconds to 60 minutes.  I have not observed correlation between wait time and queue position; it appears totally random.  In all cases, though, the queued run initially reports ??? as the time to start.

0
Comment actions Permalink

Could you please attach screenshot of Dependencies tab of build which hangs in queue and also teamcity-server.log file?

0
Comment actions Permalink

Here's a screenshot of the Dependencies tab for the first build in the chain.  As you can see, the build "1 - Build" is the first build in the chain, has no dependencies, reports one compatible agent, but cannot estimate a time to start.
overview.png
dependencies.png

I clicked around the dependency chain, and was surprised to find that the build "2 - Unit Tests" is reporting that it will never start.  I clicked into it and saw the following screenshot of its incompatible agents list.
incompatible.png

The screenshot shows that there is an implicit requirement for %dep.MicroserviceArchitecture_ZServiceHelloWorld_1Build.PatchVersion%.  This is by design for our build chain, as I want to pass the value of this parameter forward in the build chain.  I am surprised that it appears as incompatible, though.  As you can see in the next screenshot, I clearly define %PatchVersion% in the "1 - Build" configuration.
parameters.png

This leaves me with three questions.

  1. Why is "2 - Unit Tests" showing an incompatible agent?  Its parameter is defined to be the value of its snapshot dependency parameter, and the snapshot dependency does define a value for that parameter.
  2. Even if "2 - Unit Tests" can't run, why is "1 - Build" not starting right away?  "1 - Build" is the first build in the chain.  It has no dependencies and it has a compatible agent.  Shouldn't it be able to estimate a start time?
  3. In this queued run, all the builds eventually ran without any further intervention.  "1 - Build" started four minutes after queued.  "2 - Unit Tests" started about 100 seconds after "1 - Build" finished.  Why did TeamCity report that these builds would never run, but then they ran anyway?  What got them unstuck?


An excerpt of the teamcity-server.log for the relevant time window is attached.  There's some unrelated builds going on, but the relevant bits contain "ZService.HelloWorld" in it.



Attachment(s):
teamcity-server.log.zip
0
Comment actions Permalink

Hi,

Sorry for delay. It looks like you faced with this issue - https://youtrack.jetbrains.com/issue/TW-32528. Please upgrade to the latest version of TeamCity and inform us if the issue is reproduced.

0

Please sign in to leave a comment.