ALWAYS_EAGER setting broken
See original GitHub issueThis is on the latest PyPI version.
Setting CELERY_ALWAYS_EAGER = True
or TEST_RUNNER = 'djcelery.contrib.test_runner.CeleryTestSuiteRunner'
in my Django settings file doesn’t prevent Celery from sending jobs to the queue.
Issue Analytics
- State:
- Created 11 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Configuration and defaults — Celery 3.1.25 documentation
Broker settings. BROKER_URL = 'amqp://guest:guest@localhost:5672//' # List of modules to import when celery starts. CELERY_IMPORTS = ('myapp.tasks' ...
Read more >how celery_always_eager=True works? - Stack Overflow
It means Celery will not schedule tasks to run as it would regularly do, via sending a message to the broker. Instead, it...
Read more >celery.execute.send_task should respect ... - GitHub
Trying to figure out why CELERY_ALWAYS_EAGER doesn't work I found that celery.app.base.BaseApp.send_task (and thus celery.execute.send_task) doesn't respect ...
Read more >God of War Ragnarok: Where to Find Lunda's Broken Cuirass
A guide for how players can find Lunda's Broken Cuirass. ... Beyond story, Favors often give players access to a unique set of...
Read more >Broken Pieces - GOG SUPPORT CENTER
General troubleshooting · 1) Select the game in "Owned games", click the customization button in the top bar →Manage installation →Configure →Language. ·...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ask It is not that the setting isn’t read from the file – it is whether it is actually obeyed.
I suspect this is related to celery/celery#581.
I think that
librabbitmq
attempts to run tasks locally without using an AMQP server if none is available, andamqp
does simply fails if an AMQP server isn’t available.I have the same issue with django-celery==3.0.17 and Python 3.3.1. Setting
CELERY_ALWAYS_EAGER = True
explicitly insettings.py
works for me. UsingTEST_RUNNER = 'djcelery.contrib.test_runner.CeleryTestSuiteRunner'
seems not to set ALWAYS_EAGER to True.When writing unit tests you are required to set
CELERY_ALWAYS_EAGER = True
otherwise you cannot check for the calculated return values from my workers using MyTask.delay(). I would prefer using a custom TEST_RUNNER than setting the option explicitly.Currently my solution is to do the following in
settings.py