summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Add local bindep.txtqueens-eolstable/queensElod Illes2019-07-012-0/+24
| | | | | | | | | | | | | | | | | | | As it was announced [1] global bindep-fallback.txt was removed and now projects need to have a local bindep.txt to be able to install binary dependencies for testing. In test jobs the script tools/test-setup.sh is called which requires mysql and postgres servers and clients to be installed. Conflicts: tox.ini [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007272.html Change-Id: I08797a99c7ba019a4b2dd640a83f45fea8e589bd (cherry picked from commit a081180238feac761c655ece2de3b0e9b68075fa) (cherry picked from commit f460c5ac29228d373fbb623dbb57e7e030b1dcd6) (cherry picked from commit 2bb79ca9920f8409d7a04c1e2e110493fe7a62e1)
* OpenDev Migration PatchOpenDev Sysadmins2019-04-191-1/+1
| | | | | | | | | | | | | | | This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
* import zuul job settings from project-configDoug Hellmann2018-08-031-0/+12
| | | | | | | | | | | | | | | This is a mechanically generated patch to complete step 1 of moving the zuul job settings out of project-config and into each project repository. Because there will be a separate patch on each branch, the branch specifiers for branch-specific jobs have been removed. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: I440e4c8e4fb76acbb5c0d0617babb825d070fb0e Story: #2003250
* Merge "Updated from global requirements" into stable/queensZuul2018-04-262-4/+4
|\
| * Updated from global requirementsOpenStack Proposal Bot2018-02-132-4/+4
| | | | | | | | Change-Id: I691bc219e608bce832462a51583911751a7eecdc
* | don't let tox_install.sh error if there is nothing to doDoug Hellmann2018-04-231-0/+5
| | | | | | | | | | | | | | If we end up with an empty package list, return without erroring. Change-Id: Id66aaf4bcb8c40ab720303a3ca92a46f92642369 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* | Merge "Update UPPER_CONSTRAINTS_FILE for stable/queens" into stable/queensZuul2018-02-281-1/+1
|\ \
| * | Update UPPER_CONSTRAINTS_FILE for stable/queensOpenStack Release Bot2018-01-241-1/+1
| | | | | | | | | | | | Change-Id: Ic13d1f42d7147e33a19f56acf583caaf780311e1
* | | Merge "Update .gitreview for stable/queens" into stable/queensZuul2018-02-281-0/+1
|\ \ \ | |/ /
| * | Update .gitreview for stable/queensOpenStack Release Bot2018-01-241-0/+1
| |/ | | | | | | Change-Id: I3c9178e6bdc5226bf527c9edf4c65bed5c661286
* | Fix invalid json unit testBen Nemec2018-02-181-1/+5
|/ | | | | | | | | | | Recent versions of oslo.serialization have made it possible to dump exceptions to JSON, which broke a unit test in taskflow that assumed exceptions were unserializable. This change switches to an explicitly unserializable class for that test. Change-Id: If6d19bc9fcf1f1813cb087d42dc7ba6a61c71b3d Closes-Bug: 1748241 (cherry picked from commit 44ce6eae918d44c0ee85998d0526e916dee8de26)
* Merge "Add doc8 to pep8 environment"queens-em3.1.0Zuul2017-12-252-1/+11
|\
| * Add doc8 to pep8 environmentAndreas Jaeger2017-12-202-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OpenStack CI does not run the docs environment, it's just for developer convenience. Add the doc8 to the general linter environment so that it's run during automatic testing. The general linter environment is pep8. Disable testing of history.rst since generated ChangeLog file gives an error: "doc/source/user/history.rst:150: D000 Inline emphasis start-string without end-string." Readd sphinx to test environment so that doc8 passes tests. Change-Id: Ia81eac686ff3a82273b1d306596c4731c86c36e6
* | Updated from global requirementsOpenStack Proposal Bot2017-12-232-1/+4
|/ | | | Change-Id: Icb21b3ea8f9ae0eb4e51c951187756ac730251fd
* Use doc/requirements.txtAndreas Jaeger2017-12-203-6/+27
| | | | | | | | | | | | | | | The infra jobs expect documentation requirements in either doc/requirements.txt or test-requirements.txt. Since neither is available, they currently fail. Move doc requirements to doc/requirements.txt and use that to fix releasenotes build. Note that doc/requirements.txt needs some requirements for code analysis of taskflow. For the docs environment - which is a developer convenience - use the same command that is used by OpenStack CI. Change-Id: Iec65211e5059a4afdd88a45e2c1ac535b8ec97fe
* Merge "Avoid log warning when closing is underway (on purpose)"3.0.1Zuul2017-12-121-1/+8
|\
| * Avoid log warning when closing is underway (on purpose)Joshua Harlow2017-08-011-1/+8
| | | | | | | | | | | | Related-Bug: #1557107 Change-Id: I8b2f327dadbf038cd050f05fbc46a428282a3d82
* | Merge "Remove class StopWatch from timing"3.0.0Zuul2017-12-072-8/+2
|\ \
| * | Remove class StopWatch from timingchenghuiyu2017-10-242-8/+2
| | | | | | | | | | | | | | | | | | | | | | | | In new release timeutils.StopWatch can be used from oslo.uitls, so it was deprecated for removal in timing.py Change-Id: I138b8d276998a4ea2537966767cbd14f96daf757 Closes-Bug: #1715043
* | | Merge "Updated from global requirements"Zuul2017-11-202-2/+2
|\ \ \
| * | | Updated from global requirementsOpenStack Proposal Bot2017-11-162-2/+2
| | | | | | | | | | | | | | | | Change-Id: Ifcb5b175b25a265e06a2c37b9941f1251913e3b3
* | | | Remove setting of version/release from releasenotesAndreas Jaeger2017-11-161-8/+4
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release notes are version independent, so remove version/release values. We've found that projects now require the service package to be installed in order to build release notes, and this is entirely due to the current convention of pulling in the version information. Release notes should not need installation in order to build, so this unnecessary version setting needs to be removed. This is needed for new release notes publishing, see I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting at http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html . Change-Id: Iddb8f70fadf30b6094cd4d47d665bff13390394d
* | | Updated from global requirementsOpenStack Proposal Bot2017-11-151-1/+1
| | | | | | | | | | | | Change-Id: I71cf70f0482e4ddfbdd85c135c1f676b7370f80f
* | | Updated from global requirementsOpenStack Proposal Bot2017-11-121-1/+1
|/ / | | | | | | Change-Id: Ibbc774eb3345b71d8fa57fda531e62c815d0cf12
* | Merge "Remove method blather in log adapter"2.17.0Zuul2017-10-241-7/+0
|\ \
| * | Remove method blather in log adapterchenghuiyu2017-09-041-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | As method blather was using in new place, it was deprecated for removal in new release. Change-Id: Ic8d425e1774d6b7090ec105f2b37467a90c6e1e6 Closes-Bug: #1714873
* | | Merge "Remove kwarg timeout in executor conductor"Zuul2017-10-241-3/+1
|\ \ \
| * | | Remove kwarg timeout in executor conductorchenghuiyu2017-09-011-3/+1
| |/ / | | | | | | | | | | | | | | | | | | The method stop returns immediately regardless of whether the conductor has been stopped, so kwarg timeout is no longer necessary, and it is deprecated for removal. Change-Id: I50e5cbb1a00eb9b6f358f150716d2a5d682a49c9
* | | Updated from global requirements2.16.0OpenStack Proposal Bot2017-09-211-1/+1
| | | | | | | | | | | | Change-Id: I1aac1af49331ad63ef49b7b2f6b77bc55fd7a75e
* | | Merge "Updated from global requirements"Jenkins2017-09-202-4/+4
|\ \ \
| * | | Updated from global requirementsOpenStack Proposal Bot2017-09-202-4/+4
| | | | | | | | | | | | | | | | Change-Id: Id38a5dd9b8eb56c60df41725ba224c6c940793b1
* | | | Update "indentify" to "identify" in commentsluke.li2017-09-201-1/+1
|/ / / | | | | | | | | | Change-Id: I03d53ec4da681c1a4dc97fa4a636bf54a3150e2e
* | | Updated from global requirements2.15.0OpenStack Proposal Bot2017-09-112-7/+7
|/ / | | | | | | Change-Id: I41da9989b00c88543e1fe77fa994eb9f0be7a2d3
* | Updated from global requirementsOpenStack Proposal Bot2017-08-182-3/+3
|/ | | | Change-Id: I86f232684baba4c26e46f7c6b2af36b89aff0ff8
* Update reno for stable/pikeOpenStack Release Bot2017-07-282-0/+7
| | | | Change-Id: Iaf577b5692db2f3c0e144cd7e65fc34c20ded6f1
* Updated from global requirementsOpenStack Proposal Bot2017-07-271-1/+1
| | | | Change-Id: I0b6d6ae6f643c71e9395b2965ae188530f0ad563
* Updated from global requirements2.14.0OpenStack Proposal Bot2017-07-181-1/+1
| | | | Change-Id: I9f67742cb259ab22f7e36750e5008ac9d7cb87d4
* Update URLs in documents according to document migrationChangBo Guo(gcb)2017-07-137-13/+13
| | | | Change-Id: I9ca92fdcec388e02462332e04fe7c1bf8b5f64b8
* Updated from global requirementsOpenStack Proposal Bot2017-07-111-1/+1
| | | | Change-Id: I7b4861c68d441fa0fd93dd4c4d80bafb53687034
* Merge "Fix process based executor task proxying-back events"Jenkins2017-07-113-9/+87
|\
| * Fix process based executor task proxying-back eventsJoshua Harlow2017-07-113-9/+87
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's dive into what the problem is here. First a description of what happens to a task that is to be executed in a external (but local) process via the process executor mechanism. When a task is about to be sent to execute in the external (but local) process its first cloned, this is mainly done so that its notification callbacks can be altered in a safe manner (ie not altering the original task object to do this) and that clone has its notifier emptied out. What replaces the clone's notifier callbacks though is a new object (that has a __call__ method so it looks like just another callback) that will send messages to the parent process (the one that has the engine in it) over a secure(ish) channel whenever the local task triggers its notifier notify() method. This allows for callbacks in the parent process to get triggered because once the messages recieved the original tasks notifier object has its notify() method called (therefore those callbacks do not really know the task they are getting messages from is executing out of process). The issue though is that if the ANY(*) event type is registered due to how it works in the notifier is that if the child/cloned notifier has the ANY event type registered and the cloned task calls notify() with a specific event this will cause the ANY callback (in the clone) to transmit a message *and* it will cause the *specific* event callback to also transmit a message back to the parent process. On the engine process side it will get 2 messages and trigger the callbacks 3 times (twice for the specific event callback because how the local notifier has the ANY callback registered and one more time when the local process also sends the same event based on its registration of the ANY event in the child process). This is not what is expected (the message rcved on the engine process should only trigger one callback to get triggered if the engine process task has no ANY callback registered or two engine process callbacks to get triggered if the engine process task has the ANY callback registered). Closes-Bug: #1537948 Change-Id: I271bf1f23ad73df6c177cf00fd902c4881ba44ae
* | turn on warning-is-error in doc buildDoug Hellmann2017-07-085-5/+8
| | | | | | | | | | Change-Id: Id87a1b17c1986d0e30629fed13bdfbecef4a3603 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* | switch from oslosphinx to openstackdocsthemeDoug Hellmann2017-07-083-14/+18
|/ | | | | Change-Id: I7522d14d4e340f0882e41bed3528f90bbf74c2af Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* rearrange existing documentation into the new standard layoutDoug Hellmann2017-07-0835-132/+137
| | | | | Change-Id: Ic53baaa62771fda6de3b3dfe861909365103d1a9 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* Updated from global requirementsOpenStack Proposal Bot2017-06-271-1/+1
| | | | Change-Id: Id09ce74a048c3efa68242746f69d00cf7c0c3aa2
* Merge "Updated from global requirements"2.13.0Jenkins2017-06-121-1/+1
|\
| * Updated from global requirementsOpenStack Proposal Bot2017-06-101-1/+1
| | | | | | | | Change-Id: Ie2a538b5007b68fdfadb8bd7e6185edaab51b46b
* | Merge "Replace assertRaisesRegexp with assertRaisesRegex"Jenkins2017-06-1213-102/+102
|\ \
| * | Replace assertRaisesRegexp with assertRaisesRegexVu Cong Tuan2017-06-0313-102/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | assertRaisesRegexp was renamed to assertRaisesRegex in Py3.2 For more details, please check: https://docs.python.org/3/library/ unittest.html#unittest.TestCase.assertRaisesRegex Change-Id: I89cce19e80b04074aab9f49a76c7652acace78b3 Closes-Bug: #1436957
* | | Merge "Fix html_last_updated_fmt for Python3"Jenkins2017-06-121-2/+1
|\ \ \ | |_|/ |/| |
View Lorry Controller Status