Tests passing

celery/tests/worker/test_request.py

@@ -773,9 +773,7 @@ class test_TaskRequest(Case):
                     'task_id': tw.id,
                     'task_retries': 0,
                     'task_is_eager': False,
-                    'delivery_info': {'exchange': None,
-                                      'routing_key': None,
-                                      'priority': None},
+                    'delivery_info': {},
                     'task_name': tw.name})
 
     @patch('celery.worker.job.logger')

celery/tests/worker/test_worker.py

@@ -476,6 +476,7 @@ class test_Consumer(Case):
         l.update_strategies()
         l.receive_message(m.decode(), m)
         l.timer.stop()
+        l.timer.join()
 
         items = [entry[2] for entry in self.timer.queue]
         found = 0

docs/userguide/tasks.rst

@@ -219,6 +219,8 @@ The request defines the following attributes:
                 containing the exchange and routing key used to deliver this
                 task.  Used by e.g. :meth:`~@Task.retry`
                 to resend the task to the same destination queue.
+                Availability of keys in this dict depends on the
+                message broker used.
 
 
 An example task accessing information in the context is: