| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
(cherry picked from commit 4ecc391ad3d41833e0a0c13e8010e0486546fffc)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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: I3da9058ba614cd5fd45646b7d422b74cdf399b06
Story: #2003250
|
|
|
|
|
|
|
|
| |
If we end up with an empty package list, return without erroring.
Change-Id: Id66aaf4bcb8c40ab720303a3ca92a46f92642369
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
(cherry picked from commit 0c555a4126570604a68e8dc113b1ea89f611c710)
|
|
|
|
| |
Change-Id: I7abf4ded7a23464d25f66a468798aeedc3da6028
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
(cherry picked from commit 760f4414eae8fb484f4abeaee454847261228f5c)
|
|
|
|
| |
Change-Id: I63968b0b863fb4e353254182ba2daf4e0cab09be
|
|
|
|
| |
Change-Id: I734285feb42e2b1c5f5b09db56d5d7b9fd93f742
|
|
|
|
| |
Change-Id: I117ecfaca7a36e3289f58ab06299e351e611fc96
|
|
|
|
| |
Change-Id: I9f67742cb259ab22f7e36750e5008ac9d7cb87d4
|
|
|
|
| |
Change-Id: I9ca92fdcec388e02462332e04fe7c1bf8b5f64b8
|
|
|
|
| |
Change-Id: I7b4861c68d441fa0fd93dd4c4d80bafb53687034
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| | |
Change-Id: Id87a1b17c1986d0e30629fed13bdfbecef4a3603
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
|
|/
|
|
|
| |
Change-Id: I7522d14d4e340f0882e41bed3528f90bbf74c2af
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
|
|
|
|
|
| |
Change-Id: Ic53baaa62771fda6de3b3dfe861909365103d1a9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
|
|
|
|
| |
Change-Id: Id09ce74a048c3efa68242746f69d00cf7c0c3aa2
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ie2a538b5007b68fdfadb8bd7e6185edaab51b46b
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
html_last_updated_fmt option is interpreted as a
byte string in python3, causing Sphinx build to break.
This patch makes it utf-8 string.
Changing Popen to .check_output because of 3 reasons:
1. check_output() will raise CalledProcessError if
the called process returns a non-zero return code.
2. For consistency with keystone [1] and cinder [2]
3. It makes the code look much better.
[1] https://review.openstack.org/#/c/457142/
[2] https://review.openstack.org/#/c/433081
Change-Id: I6e9c2009f224abc282acbf957d7e999c7f87e9eb
|
|/
|
|
| |
Change-Id: Idec10de780faa6ef1b917816c733a4069f89020f
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Running a nonblocking conductor or two conductors on the same host will re-execute the same job multiple times with the current implementation of 'claim' for the redis jobboard backend. This is different from the ZooKeeper jobboard backend, there the same owner of a job is not allowed to reclaim the job again (https://github.com/openstack/taskflow/blob/master/taskflow/jobs/backends/impl_zookeeper.py#L554). If the same owner is allowed to reclaim the job again there can be no concurrent execution on the same owner because all jobs will be re-claimed and re-executed by the same owner every pass as long as it's on the jobboard.
To reproduce this behavior:
- Use the redis jobboard backend
- Create a flow with a task that sleeps 10 seconds in the execute method
- Post that flow as a job
- Run a nonblocking conductor
It will claim and execute the same job multiple times in a loop until the first worker is finished and consumes the job. After this change it will not re-execute the same job multiple times.
Change-Id: I4f6c364211500e510fc496f23b03ce056771417d
|
|/
|
|
| |
Change-Id: Ifad39a3cf765807bd3d6a006a5e9ce5ad0e5d1ce
|
|\ |
|
| |
| |
| |
| |
| |
| | |
This module has been deprecated in favor of native fixtures.
Change-Id: I40ed7360091fea51a257807035e923c85602949f
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: I5d93bd4d2185c8f464f04772fa35618f5775a3d9
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
python3.0 has deprecated LOG.warn
https://docs.python.org/3/library/logging.html#logging.warning
Closes-Bug: #1650843
Change-Id: Ib8473cbdb84547f385e619fe08ed723b1ee7bcdb
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
dict.keys() returns object dict_keys on Python 3, can't work well
with kombu recently, convert it to list before futhur processing.
Closes-Bug: #1687855
Change-Id: I9dcfadd8f16eccce06f4cde3b2a6669f28a3f8bc
|
|/
|
|
| |
Change-Id: I079d77ea0e59a7abe611b923afadfcefa3d972ae
|
|
|
|
| |
Change-Id: I133cd4cbcc518a903b061768b7fb9a91a6fe44e6
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I5771b84b59cbf2e2d65f7f8b4d64036fde0a89b9
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
TrivialFix
Change-Id: I7c9f2dc507641a03717333a5e0c0479f96379326
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | | |
Change-Id: I8bd162d9482600d29d15ab6f54526b3324a10e32
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add simple script to setup mysql and postgresql databases, this script
can be run by users during testing and will be run by CI systems for
specific setup before running unit tests. This is exactly what is
currently done by OpenStack CI in project-config.
This allows to change in project-config the python-db jobs to
python-jobs since python-jobs will call this script initially.
See also
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html
Needed-By: I1c6c23b39a93991d2dcb5e753fd851d244326581
Change-Id: Ibbe9910b0bae398542bf5fb84f2c7151bc898770
|
|/
|
|
| |
Change-Id: Ie24dbe03673525b8a7216b47a4f4222fd5df330b
|
|
|
|
|
|
|
|
|
| |
Lock down the various state machine action handling
functions so that they are ensured correct (and consistent)
access to the storage layer when they are modifiying and/or
reading it.
Change-Id: Ie893a44aa963ab515f19e77f9904f49c843cb4e5
|
|
|
|
|
|
|
| |
This has been moved into the futurist lib
and is no longer imported by taskflow.
Change-Id: I1c1c6817d5bd472ebcc958338332f140cc069601
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This moves out the engine next to run (or revert)
selection process to a single class that just does
this and moves out the common functions the analyzer
class provided to the runtime object (which all
components can access).
This makes it easier to adjust the selection algorithm
in different ways.
Change-Id: I091c69297a7bff60729791d3ca6c3fae14d6eea5
|
|
|
|
|
|
|
| |
Change author to OpenStack and author-email to
openstack-dev@lists.openstack.org
Change-Id: Ie8812ceac8d79a3c1697e2ecf5e4fd4d1378477e
|
|
|
|
| |
Change-Id: Ie656000c4fd281565944a8d21cc766e98e7b53d8
|