9b41a0b502
This addresses a recent increase in test_idle failures. The existing apscheduler was not being shut down during reconfigurations which caused us to end up with two apschedulers running during the test. This could cause a trigger event to fire while the test was expecting the system to be idle. The triggers were not previously shut down during reconfigurations. Instead, the timer trigger relied on having its postConfig method called on each reconfiguration, where it would begin by cleaning up any existing jobs. However, since the connections changes, triggers are stopped, discarded, and recreated during reconfiguration. Because the stop method of the timer trigger was not actually being called, a new trigger was created each time we reconfigured, and old ones were never cleaned up. This likely had a production impact as well, however, it was not likely to be visible unless a configuration change altered the scheduled times for periodic queues (in that case, we would see jobs run at both the old and new times). Change-Id: Ia7c61984a9c47a9b1554a4ccb99309674dffec11 |
||
---|---|---|
doc | ||
etc | ||
tests | ||
tools | ||
zuul | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
LICENSE | ||
MANIFEST.in | ||
NEWS.rst | ||
README.rst | ||
TESTING.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Zuul
Zuul is a trunk gating system developed for the OpenStack Project.
Contributing
To browse the latest code, see: https://git.openstack.org/cgit/openstack-infra/zuul/tree/ To clone the latest code, use git clone git://git.openstack.org/openstack-infra/zuul
Bugs are handled at: https://storyboard.openstack.org/#!/project/679
Code reviews are, as you might expect, handled by gerrit. The gerrit they use is http://review.openstack.org
Use git review to submit patches (after creating a gerrit account that links to your launchpad account). Example:
# Do your commits
$ git review
# Enter your username if prompted