Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pending builds are not kicking #2937

Closed
tardyp opened this issue Mar 9, 2017 · 4 comments
Closed

pending builds are not kicking #2937

tardyp opened this issue Mar 9, 2017 · 4 comments

Comments

@tardyp
Copy link
Member

tardyp commented Mar 9, 2017

This ticket is a migrated Trac ticket 3265

People contributed to the original ticket: @djmitche, benoit.allard@...
Ticket created on: May 26 2015
Ticket last modified on: Sep 06 2015


I configured some new builders, and reloaded the configs, builders appear everything looks good. Later I wondered why no build where scheduled on those builders, and why the requests are queueing up. My one slave is up and processing builds from other builders.

Upon a master restart, all pending builds are being kicked.

I have no idea what the problem was / is, and realize that my problem description might not help much.


Comment from: @dustin
Date: Sep 06 2015

We had another issue like this around latent slaves with wait_time=0. Is that the case here?

@tardyp tardyp added this to the 0.9.+ milestone Mar 9, 2017
@PunChaFeng
Copy link
Contributor

@seankelly, I encountered the same issue. I can give you some hint.

  1. I add only one Latent Slave/Worker and set its build_wait_timeout to 0. So, for each job, buildbot should substantiate a new VM and insubstantiate it after build is finished.
  2. I queue two jobs at once.
  3. The slave picks up the first job and starts substantiate an VM to build.
  4. Once the build is finished, buildbot is insubstantiating it and in the meanwhile, maybeStartBuild() function is called to ask the slave whether it is ready to pick another job. Since the latent slave is insubstantiating, so the answer is no. The second jobs are not picked and keep Pending.

@tardyp
Copy link
Member Author

tardyp commented Jun 8, 2017

@PunChaFeng which version of buildbot are you working on?

@PunChaFeng
Copy link
Contributor

@tardyp I'm using 0.8.7p1

@tardyp
Copy link
Member Author

tardyp commented Jun 9, 2017

Buildbot 0.8.7p1 was released on November 21, 2012. A lot happen since then and this bug was fixed.
I you want to use LatentWorker, please use buildbot >0.9.3

@tardyp tardyp closed this as completed Jun 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants