Celery RuntimeWarning E_WOULDBLOCK

[hackdna]

• Specific code commit: e2bb3a6
• Version of the web browser and OS: N/A
• Environment where the error occurred: Vagrant and AWS

Steps to reproduce

Run an analysis

Observed behavior

Celery worker1 log:

2019-04-11 12:20:28,898 DEBUG    analysis_manager.tasks:368 _run_galaxy_workflow[88ef5845-5d71-49cb-8816-551245466b68] - Starting workflow execution in Galaxy
/home/vagrant/.virtualenvs/refinery-platform/local/lib/python2.7/site-packages/celery/result.py:45: RuntimeWarning: Never call result.get() within a task!
See http://docs.celeryq.org/en/latest/userguide/tasks.html#task-synchronous-subtasks

In Celery 3.2 this will result in an exception being
raised instead of just being a warning.

  warnings.warn(RuntimeWarning(E_WOULDBLOCK))

2019-04-11 12:20:28,901 WARNING  py.warnings:45 assert_will_not_block() - /home/vagrant/.virtualenvs/refinery-platform/local/lib/python2.7/site-packages/celery/result.py:45: RuntimeWarning: Never call result.get() within a task!
See http://docs.celeryq.org/en/latest/userguide/tasks.html#task-synchronous-subtasks

In Celery 3.2 this will result in an exception being
raised instead of just being a warning.

  warnings.warn(RuntimeWarning(E_WOULDBLOCK))

2019-04-11 12:20:34,864 INFO     analysis_manager.tasks:289 run_analysis[88ef5845-5d71-49cb-8816-551245466b68] - Executing Analysis with UUID: baf1ef2b-02aa-4200-8871-e4d7f25c76ea

This will prevent Celery upgrade to versions higher than 3.1.x and can lead to very hard to diagnose task execution failures.

Expected behavior

No warning or error.