[users at bb.net] [SPAM] How to debug why the buildmaster won't start a build?

[Pierre Tardy]

If you see the message "adding buildset 183 to database" I would expect
that buildrequests are created.

If I look at your database:

last ten buildsets: all are completed
https://alan.ci/buildbot/api/v2/buildsets?order=-bsid&limit=10

last ten buildrequests: all are completed
https://alan.ci/buildbot/api/v2/buildrequests?order=-buildrequestid&limit=10

So I would say that your builds are actually run.
maybe your scheduler is not scheduling what you want?

I can see in your UI that some builds started 15min ago. is this resolved?

On Tue, Jun 13, 2017 at 5:01 PM alan somers <asomers at gmail.com> wrote:

> Nope, no buildrequests either.
> https://alan.ci/buildbot/#/builders/5
>
> The only worker is a DockerLatentWorker.  I've verified that the
> buildmaster can talk to the Docker server, and I can't find any
> docker-related error messages in twistd.log.  So I think the problem
> is that the master isn't generating any BuildRequests.  What might be
> causing that?
>
> -Alan
>
> On Tue, Jun 13, 2017 at 8:57 AM, Pierre Tardy <tardyp at gmail.com> wrote:
> > The home page only show the running builds.
> > in the builder page, there is the list of buildrequests.
> >
> > A reason why a master won't start them might be
> > - there is no worker available
> > - there is a nextWorker or a nextBuild callback which returns None or []
> >
> > In the case those checks do not help, the code where you can start to add
> > debug logs is:
> >
> https://github.com/buildbot/buildbot/blob/master/master/buildbot/process/buildrequestdistributor.py#L189
> >
> > Regards
> > Pierre
> >
> > On Tue, Jun 13, 2017 at 4:49 PM alan somers <asomers at gmail.com> wrote:
> >>
> >> No, the home page shows no pending builds.
> >>
> >> On Tue, Jun 13, 2017 at 8:46 AM, Neil Gilmore <ngilmore at grammatech.com>
> >> wrote:
> >> > Alan,
> >> >
> >> > Does your setup have a web UI? If so, are you seeing builds being
> >> > queued?
> >> > Big difference between a queued build not starting and builds not
> >> > getting
> >> > queued at all...
> >> >
> >> > Neil Gilmore
> >> > grammatech.com
> >> >
> >> >
> >> > On 6/12/2017 11:12 PM, alan somers wrote:
> >> >>
> >> >> I have a buildmaster with one DockerLatentWorker and two builders.
> >> >> Each builder has two change sources: a GitPoller and a
> >> >> GitHubPullrequestPoller.  Each builder also has two schedulers: an
> >> >> AnyBranchScheduler for a few select branches and an
> AnyBranchScheduler
> >> >> for pull requests.  I also have Github hooks setup to push commit
> >> >> notifications into the buildmaster.  There is a WorkerLock with a
> >> >> maxCount of 1 that is shared by one step of both builders'
> >> >> BuilderConfigs.
> >> >>
> >> >> Everything was working fine until today, but now the buildmaster
> never
> >> >> attempts to kick off a build.  I can see from twistd.log that the
> >> >> GitHub hook is still working, and I see log entries like "added
> >> >> buildset 183 to database".  However, whereas normally that entry
> would
> >> >> be followed up by a "starting build" entry, now there is nothing.
> >> >> There aren't any errors; there's just nothing at all.
> >> >>
> >> >> How can I debug this problem?  I have Manhole working, but I don't
> >> >> know what to look for.  Any advice would be appreciated.
> >> >>
> >> >> Buildless in Boulder,
> >> >> -Alan
> >> >> _______________________________________________
> >> >> users mailing list
> >> >> users at buildbot.net
> >> >> https://lists.buildbot.net/mailman/listinfo/users
> >> >
> >> >
> >> > _______________________________________________
> >> > users mailing list
> >> > users at buildbot.net
> >> > https://lists.buildbot.net/mailman/listinfo/users
> >> _______________________________________________
> >> users mailing list
> >> users at buildbot.net
> >> https://lists.buildbot.net/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20170613/05bccee2/attachment.html>