-
Notifications
You must be signed in to change notification settings - Fork 39
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
tests: conflict between CliRunner and Celery in memory broker #40
Comments
nharraud
pushed a commit
to nharraud/invenio-indexer
that referenced
this issue
Sep 7, 2016
* FIX Fixes tests by using rabbitmq instead of in memory queue. (closes inveniosoftware#40) Signed-off-by: Nicolas Harraudeau <nicolas.harraudeau@cern.ch>
nharraud
pushed a commit
to nharraud/invenio-indexer
that referenced
this issue
Sep 7, 2016
* FIX Fixes tests by using rabbitmq instead of in memory queue. (closes inveniosoftware#40) Signed-off-by: Nicolas Harraudeau <nicolas.harraudeau@cern.ch>
nharraud
pushed a commit
to nharraud/invenio-indexer
that referenced
this issue
Sep 7, 2016
* FIX Fixes tests by using rabbitmq instead of in memory queue. (closes inveniosoftware#40) Signed-off-by: Nicolas Harraudeau <nicolas.harraudeau@cern.ch>
jirikuncar
pushed a commit
that referenced
this issue
Sep 15, 2016
* FIX Fixes tests by using rabbitmq instead of in memory queue. (closes #40) Signed-off-by: Nicolas Harraudeau <nicolas.harraudeau@cern.ch>
jirikuncar
pushed a commit
that referenced
this issue
Sep 15, 2016
* Fixes tests by using rabbitmq instead of in memory queue. (closes #40) Signed-off-by: Nicolas Harraudeau <nicolas.harraudeau@cern.ch>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I run the tests I get the exception:
After some more digging it looks like two delete messages are queued when one is published here
This only happens when
tests/test_cli.py::test_reindex
is ran beforetests/test_utils.py::test_record_indexing
like this:py.test tests/test_cli.py::test_reindex tests/test_utils.py::test_record_indexing
If
tests/test_utils.py::test_record_indexing
alone is ran then the issue does not appear.I tracked down the issue to the
BROCKER_URL
config variable. The problem arises only withBROKER_URL=os.environ.get('BROKER_URL', 'memory://')
but not with rabbitmq or redis.The text was updated successfully, but these errors were encountered: