<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Pierre,<br>
<br>
On 9/8/2016 2:34 PM, Pierre Tardy wrote:<br>
<blockquote
cite="mid:CAJ+soVcHbEL_d+H7x7cJME0LmFQnY+NevaixccSnFf+DTau0xw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<br>
<div class="gmail_quote">
<div dir="ltr">Le jeu. 8 sept. 2016 à 18:25, Neil Gilmore <<a
moz-do-not-send="true"
href="mailto:ngilmore@grammatech.com">ngilmore@grammatech.com</a>>
a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi Pierre,<br>
<br>
Thanks for the quick reply.<br>
</div>
</blockquote>
<div>no problem, it is important for me to track all issues
quickly as we are coming very near the release.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
I went over this again, and no steps was not the real
problem. The real problem was that we are creating a
worker name that doesn't exist. The other builders use the
correct name, but this one doesn't. I don't recall seeing
any exceptions or logging related to this, but I suppose I
wouldn't, as the master doesn't know when it starts up who
might connect to it.<br>
</div>
</blockquote>
<div><br>
</div>
<div>What do you mean by worker name that does not exist?</div>
<div>Normally you cannot start the master if it has builder
connected to non-existant worker. </div>
<div><a moz-do-not-send="true"
href="https://github.com/buildbot/buildbot/blob/master/master/buildbot/config.py#L825">https://github.com/buildbot/buildbot/blob/master/master/buildbot/config.py#L825</a><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><br>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
I probably said that badly, or at least not clearly.<br>
<br>
There's no technical problem with master.cfg, and this is not an
error in buildbot.<br>
<br>
What we have is a situation where there's no worker process that
thinks it has a name that matches one in master.cfg.<br>
<br>
We have a host that runs a worker. That worker has a workername in
its buildbot.tac.<br>
<br>
We have a master whose master.cfg has a matching entry in
c['workers'] that matches that name. We even have a builder that
specifies that name, and it schedules and builds.<br>
<br>
But someone created a c['workers'] entry with a different name, even
though they didn't intend for it to be a different name (the process
is indirect in our master.cfg). The different name is used by a
builder. Nothing happens because the master is really waiting for a
worker by that name to connect, which will never happen. I imagine
that if I DID start up a worker process with this different name,
the master would start having it do the build.<br>
<br>
Neil Gilmore<br>
grammatech.com<br>
</body>
</html>