Ignore the call to the profilers disable method in the ProfilingPanel.

While this hasn't caused any issues with the actual usage of the
toolbar, it has caused an unexpected error within the unit tests.
This is because the dictionary returned by stats is converted into
a list. The order of this list isn't consistent, while the logic
expects it to which gave it the random feel to it.

Ignoring the call to the disable should cause the view function
to be the only function with zero callers.

Author: tim-schilling

debug_toolbar/panels/profiling.py

@@ -10,14 +10,19 @@
 from colorsys import hsv_to_rgb
 import os
 
+# Occasionally the disable method on the profiler is listed before
+# the actual view functions. This function call should be ignored as
+# it leads to an error within the tests.
+INVALID_PROFILER_FUNC = "<method 'disable' of '_lsprof.Profiler' objects>"
+
 
 class DjangoDebugToolbarStats(Stats):
     __root = None
 
     def get_root_func(self):
         if self.__root is None:
             for func, (cc, nc, tt, ct, callers) in self.stats.items():
-                if len(callers) == 0:
+                if len(callers) == 0 and INVALID_PROFILER_FUNC not in func:
                     self.__root = func
                     break
         return self.__root

tests/panels/test_profiling.py

@@ -7,7 +7,6 @@
 
 from ..base import BaseTestCase
 from ..views import regular_view
-from debug_toolbar.compat import unittest
 
 
 @override_settings(DEBUG_TOOLBAR_PANELS=['debug_toolbar.panels.profiling.ProfilingPanel'])
@@ -17,9 +16,6 @@ def setUp(self):
         super(ProfilingPanelTestCase, self).setUp()
         self.panel = self.toolbar.get_panel_by_id('ProfilingPanel')
 
-    # This test fails randomly for a reason I don't understand.
-
-    @unittest.expectedFailure
     def test_regular_view(self):
         self.panel.process_view(self.request, regular_view, ('profiling',), {})
         self.panel.process_response(self.request, self.response)