title: Python Django Rest Framework UnorderedObjectListWarning
body: <p>I upgraded from Django 1.10.4 to 1.11.1 and all of a sudden I'm getting a ton of these messages when I run my tests:</p>
  
  <pre><code>lib/python3.5/site-packages/rest_framework/pagination.py:208:
  UnorderedObjectListWarning: 
  Pagination may yield inconsistent results with an unordered object_list: 
  &lt;QuerySet [&lt;Group: Requester&gt;]&gt;
  paginator = self.django_paginator_class(queryset, page_size)
  </code></pre>
  
  <p>I've traced that back to the Django Pagination module:
  <a href="https://github.com/django/django/blob/master/django/core/paginator.py#L100" rel="noreferrer">https://github.com/django/django/blob/master/django/core/paginator.py#L100</a></p>
  
  <p>It seems to be related to my queryset code:</p>
  
  <pre><code>return get_user_model().objects.filter(id=self.request.user.id)
  </code></pre>
  
  <p>How can I find more details on this warning?  It seems to be that I need to add a <code>order_by(id)</code> on the end of every filter, but I can't seem to find which code needs the order_by added (because the warning doesn't return a stack trace and so it happens randomly during my test run).  </p>
  
  <p>Thanks!</p>
  
  <p>Edit:</p>
  
  <p>So by using @KlausD. verbosity tip, I looked at a test causing this error:</p>
  
  <p><code>response = self.client.get('/api/orders/')</code></p>
  
  <p>This goes to <code>OrderViewSet</code> but none of the things in get_queryset cause it and nothing in serializer class causes it.  I have other tests that use the same code to get /api/orders and those don't cause it....  What does DRF do after get_queryset?</p>
  
  <p><a href="https://github.com/encode/django-rest-framework/blob/master/rest_framework/pagination.py#L166" rel="noreferrer">https://github.com/encode/django-rest-framework/blob/master/rest_framework/pagination.py#L166</a></p>
  
  <p>If I put a traceback into pagination then I get a whole bunch of stuff related to django rest framework but nothing that points back to which of my queries is triggering the order warning.</p>