Fix HistoryTest.testForge on Win...

chrome/test/functional/history.py

Index: chrome/test/functional/history.py
===================================================================
--- chrome/test/functional/history.py	(revision 51546)
+++ chrome/test/functional/history.py	(working copy)
@@ -183,8 +183,12 @@
     history = self.GetHistoryInfo().History()
     self.assertEqual(1, len(history))
     self.assertTrue('zoinks' in history[0]['url'])  # yes it gets lower-cased.
+    # Python's time might be slightly off (~10 ms) from Chrome's time (on win).
+    # time.time() on win counts in 1ms steps whereas it's 1us on linux.
+    # So give the new history item some time separation, so that we can rely
+    # on the history ordering.
+    now = time.time() + 5

[John Grabowski, 2010/07/02 23:53:02]

perhaps refactor into a routine called getNextTime() or whatever that is defined
to "get a time later than any previously returned time".  Makes things more
clear than just "+5".

def getNextTime(self):
  x = time.time()
  while True:
    y = time.time()
    if y == x:
      y += 1
    x = y
    yield y

[Nirnimesh, 2010/07/03 00:15:18]

Part of the problem is that Chrome's time is slightly out of sync with python's
time.
So when I add a history item "now" (at python time = 1.2345) it gets added in
chromium with time~=1.2445, and then you do add the next history item giving it
time=1.2400, which is still newer than 1.2445. And the ordering is still
reversed. :(

     # Full interface (specify both title and url)
-    now = time.time()
     self.AddHistoryItem({'title': 'Google',
                          'url': 'http://www.google.com',
                          'time': now})