<div dir="ltr">If you see the message "adding buildset 183 to database" I would expect that buildrequests are created.<div><br></div><div>If I look at your database:</div><div><br></div><div>last ten buildsets: all are completed</div><div><a href="https://alan.ci/buildbot/api/v2/buildsets?order=-bsid&limit=10">https://alan.ci/buildbot/api/v2/buildsets?order=-bsid&limit=10</a><br></div><div><br></div><div>last ten buildrequests: all are completed</div><div><a href="https://alan.ci/buildbot/api/v2/buildrequests?order=-buildrequestid&limit=10">https://alan.ci/buildbot/api/v2/buildrequests?order=-buildrequestid&limit=10</a></div><div><br><div>So I would say that your builds are actually run.</div></div><div>maybe your scheduler is not scheduling what you want?</div><div><br></div><div>I can see in your UI that some builds started 15min ago. is this resolved?</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 13, 2017 at 5:01 PM alan somers <<a href="mailto:asomers@gmail.com">asomers@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nope, no buildrequests either.<br>
<a href="https://alan.ci/buildbot/#/builders/5" rel="noreferrer" target="_blank">https://alan.ci/buildbot/#/builders/5</a><br>
<br>
The only worker is a DockerLatentWorker. I've verified that the<br>
buildmaster can talk to the Docker server, and I can't find any<br>
docker-related error messages in twistd.log. So I think the problem<br>
is that the master isn't generating any BuildRequests. What might be<br>
causing that?<br>
<br>
-Alan<br>
<br>
On Tue, Jun 13, 2017 at 8:57 AM, Pierre Tardy <<a href="mailto:tardyp@gmail.com" target="_blank">tardyp@gmail.com</a>> wrote:<br>
> The home page only show the running builds.<br>
> in the builder page, there is the list of buildrequests.<br>
><br>
> A reason why a master won't start them might be<br>
> - there is no worker available<br>
> - there is a nextWorker or a nextBuild callback which returns None or []<br>
><br>
> In the case those checks do not help, the code where you can start to add<br>
> debug logs is:<br>
> <a href="https://github.com/buildbot/buildbot/blob/master/master/buildbot/process/buildrequestdistributor.py#L189" rel="noreferrer" target="_blank">https://github.com/buildbot/buildbot/blob/master/master/buildbot/process/buildrequestdistributor.py#L189</a><br>
><br>
> Regards<br>
> Pierre<br>
><br>
> On Tue, Jun 13, 2017 at 4:49 PM alan somers <<a href="mailto:asomers@gmail.com" target="_blank">asomers@gmail.com</a>> wrote:<br>
>><br>
>> No, the home page shows no pending builds.<br>
>><br>
>> On Tue, Jun 13, 2017 at 8:46 AM, Neil Gilmore <<a href="mailto:ngilmore@grammatech.com" target="_blank">ngilmore@grammatech.com</a>><br>
>> wrote:<br>
>> > Alan,<br>
>> ><br>
>> > Does your setup have a web UI? If so, are you seeing builds being<br>
>> > queued?<br>
>> > Big difference between a queued build not starting and builds not<br>
>> > getting<br>
>> > queued at all...<br>
>> ><br>
>> > Neil Gilmore<br>
>> > <a href="http://grammatech.com" rel="noreferrer" target="_blank">grammatech.com</a><br>
>> ><br>
>> ><br>
>> > On 6/12/2017 11:12 PM, alan somers wrote:<br>
>> >><br>
>> >> I have a buildmaster with one DockerLatentWorker and two builders.<br>
>> >> Each builder has two change sources: a GitPoller and a<br>
>> >> GitHubPullrequestPoller. Each builder also has two schedulers: an<br>
>> >> AnyBranchScheduler for a few select branches and an AnyBranchScheduler<br>
>> >> for pull requests. I also have Github hooks setup to push commit<br>
>> >> notifications into the buildmaster. There is a WorkerLock with a<br>
>> >> maxCount of 1 that is shared by one step of both builders'<br>
>> >> BuilderConfigs.<br>
>> >><br>
>> >> Everything was working fine until today, but now the buildmaster never<br>
>> >> attempts to kick off a build. I can see from twistd.log that the<br>
>> >> GitHub hook is still working, and I see log entries like "added<br>
>> >> buildset 183 to database". However, whereas normally that entry would<br>
>> >> be followed up by a "starting build" entry, now there is nothing.<br>
>> >> There aren't any errors; there's just nothing at all.<br>
>> >><br>
>> >> How can I debug this problem? I have Manhole working, but I don't<br>
>> >> know what to look for. Any advice would be appreciated.<br>
>> >><br>
>> >> Buildless in Boulder,<br>
>> >> -Alan<br>
>> >> _______________________________________________<br>
>> >> users mailing list<br>
>> >> <a href="mailto:users@buildbot.net" target="_blank">users@buildbot.net</a><br>
>> >> <a href="https://lists.buildbot.net/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.buildbot.net/mailman/listinfo/users</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > users mailing list<br>
>> > <a href="mailto:users@buildbot.net" target="_blank">users@buildbot.net</a><br>
>> > <a href="https://lists.buildbot.net/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.buildbot.net/mailman/listinfo/users</a><br>
>> _______________________________________________<br>
>> users mailing list<br>
>> <a href="mailto:users@buildbot.net" target="_blank">users@buildbot.net</a><br>
>> <a href="https://lists.buildbot.net/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.buildbot.net/mailman/listinfo/users</a><br>
</blockquote></div>