Message170411
First off, that assertEquals should have a custom error message stating what values the date objects had to better tell how off things were.
Second, this can probably be solved by upping the timedelta to something like a minute or something for when it's run on a really slow machine (I mean the test itself is wonky based on the the definition of date.today() and not being able to freeze time, so being upwards of a minute off should be acceptable to verify it's still "today"). |
|
Date |
User |
Action |
Args |
2012-09-12 17:39:29 | brett.cannon | set | recipients:
+ brett.cannon, belopolsky, pitrou |
2012-09-12 17:39:29 | brett.cannon | set | messageid: <1347471569.16.0.344244114185.issue15933@psf.upfronthosting.co.za> |
2012-09-12 17:39:28 | brett.cannon | link | issue15933 messages |
2012-09-12 17:39:28 | brett.cannon | create | |
|