<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Pierre,<br>
<br>
In our case, restarting masters is annoying to others. It may be
better for us to switch back to the original branch and reconfigure
(because we don't actually care if any of those builds schedules).
This should remove the scheduler we don't want. Switch back to the
current branch and reconfigure, and all the master should have the
correct builders.<br>
<br>
Our base problem is that a couple of builders were switched to the
new branch a while ago, which is why the scheduler of that name
existed. When we switched branches for the rest of the builders,
they never got in because that scheduler already existed.<br>
<br>
Neil Gilmore<br>
grammatech.com<br>
<br>
<div class="moz-cite-prefix">On 11/4/2016 11:02 AM, Pierre Tardy
wrote:<br>
</div>
<blockquote
cite="mid:CAJ+soVcnKf2qs1KLDxt+P1aRyzu3NLMtmb+ykQ_R+_tZaAvjqQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hi Neil and Pieter,
<div><br>
</div>
<div>This is a known problem in buildbot nine that schedulers
are not reconfigurable.</div>
<div>The need to implement the reconfigureService API, which
they don't.</div>
<div>This is not a big amount of work, but this has not been
done yet.</div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://trac.buildbot.net/ticket/2237">http://trac.buildbot.net/ticket/2237</a><br>
</div>
<div><br>
</div>
<div>The workaround is to change the scheduler name so that it
is forced re-created.</div>
<div>Please feel free to dig in the code and submit a PR if this
becomes too annoying.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Pierre</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">Le ven. 4 nov. 2016 à 16:51, 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">(managed to
not reply to the list the first time...)<br class="gmail_msg">
<br class="gmail_msg">
On 11/4/2016 9:02 AM, Neil Gilmore wrote:<br class="gmail_msg">
> Hi Pieter,<br class="gmail_msg">
><br class="gmail_msg">
> Thanks for the reply and explanation. It's nice to know
that someone<br class="gmail_msg">
> else experiences this.<br class="gmail_msg">
><br class="gmail_msg">
> It would also explain a previous problem we had where
someone updated<br class="gmail_msg">
> the configuration to move a daily builder to a new time,
and it would<br class="gmail_msg">
> never schedule.<br class="gmail_msg">
><br class="gmail_msg">
> I can do restarts, but it's socially painful (people
notice and<br class="gmail_msg">
> complain immediately). Keeping history isn't a problem,
though, as we<br class="gmail_msg">
> send all our build results to a different, more
comprehensive system.<br class="gmail_msg">
><br class="gmail_msg">
> Neil Gilmore<br class="gmail_msg">
> <a moz-do-not-send="true" href="http://grammatech.com"
rel="noreferrer" class="gmail_msg" target="_blank">grammatech.com</a><br
class="gmail_msg">
><br class="gmail_msg">
> On 11/4/2016 2:48 AM, Pieter Lexis wrote:<br
class="gmail_msg">
>> Hello Neil,<br class="gmail_msg">
>><br class="gmail_msg">
>> On Thu, 3 Nov 2016 16:27:11 -0500<br
class="gmail_msg">
>> Neil Gilmore <<a moz-do-not-send="true"
href="mailto:ngilmore@grammatech.com" class="gmail_msg"
target="_blank">ngilmore@grammatech.com</a>> wrote:<br
class="gmail_msg">
>><br class="gmail_msg">
>>> It seems that after a branch change and reconfig,
our buildbot<br class="gmail_msg">
>>> system is<br class="gmail_msg">
>>> misbehaving. Builds are not getting scheduled.<br
class="gmail_msg">
>>> <SNIP><br class="gmail_msg">
>> I have been experiencing similar 'issues' since beta
2 (I believe). I<br class="gmail_msg">
>> don't update the configuration often, so I hardly
notice. This is<br class="gmail_msg">
>> with a single master.<br class="gmail_msg">
>><br class="gmail_msg">
>> But e.g. adding a builder to a scheduler and
reloading the config. It<br class="gmail_msg">
>> appears that that this is not picked up. After a
restart (which I can<br class="gmail_msg">
>> do on the platform I'm running), all is well.<br
class="gmail_msg">
>> However, I once forgot to restart and noticed the
next day that after<br class="gmail_msg">
>> some time the changes were picked up, leading me to
believe that<br class="gmail_msg">
>> buildbot might keep some old state around, although I
have not been<br class="gmail_msg">
>> able to reproduce this in a test environment.<br
class="gmail_msg">
>><br class="gmail_msg">
>> Best regards,<br class="gmail_msg">
>><br class="gmail_msg">
>> Pieter<br class="gmail_msg">
>><br class="gmail_msg">
><br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br
class="gmail_msg">
users mailing list<br class="gmail_msg">
<a moz-do-not-send="true" href="mailto:users@buildbot.net"
class="gmail_msg" target="_blank">users@buildbot.net</a><br
class="gmail_msg">
<a moz-do-not-send="true"
href="https://lists.buildbot.net/mailman/listinfo/users"
rel="noreferrer" class="gmail_msg" target="_blank">https://lists.buildbot.net/mailman/listinfo/users</a><br
class="gmail_msg">
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>