logilab-common v0.50.1 and .2
When test suite is executed and date is 2010-05-24 (you can replicate changing the date of your machine) it fails with:
========================= unittest_date.py =========================
..............F....................F.....
======================================================================
FAIL: test_open_days_now_now (unittest_date.DateTC)
----------------------------------------------------------------------
Traceback (most recent call last)
File "/tmp/buildd/logilab-common-0.50.2/test/unittest_date.py", line 115, in test_open_days_now_now
self.assertOpenDays(x, x, 0)
File "/tmp/buildd/logilab-common-0.50.2/test/unittest_date.py", line 80, in assertOpenDays
self.assertEquals(got, expected)
File "/usr/lib/python2.5/unittest.py", line 334, in failUnlessEqual
(msg or '%r != %r' % (first, second))
AssertionError: -1 != 0
======================================================================
FAIL: test_open_days_now_now (unittest_date.MxDateTC)
----------------------------------------------------------------------
Traceback (most recent call last)
File "/tmp/buildd/logilab-common-0.50.2/test/unittest_date.py", line 115, in test_open_days_now_now
self.assertOpenDays(x, x, 0)
File "/tmp/buildd/logilab-common-0.50.2/test/unittest_date.py", line 80, in assertOpenDays
self.assertEquals(got, expected)
File "/usr/lib/python2.5/unittest.py", line 334, in failUnlessEqual
(msg or '%r != %r' % (first, second))
AssertionError: -1 != 0
I've tried to test with date set to 2010-05-25 (yesterday), 2010-05-26 (today), 2010-05-31 (the next monday), 2010-06-24 (the 24th day of the next month) but all of them were executed just fine.
Regards,
Sandro
|