chromite: Fix ParseDateTest.testBasicFunctionality for 2018.
Update merge_logs_unittest.py's
ParseDateTest.testBasicFunctionality test, which had a
hardcoded assumption that the current year is 2017.
I think it'll still be possible for the updated test to fail
if we cross a year boundary between its merge_logs.ParseDate
and datetime.datetime.now calls. That's unlikely to happen,
but the right fix is probably to make ParseDate also take
the current time.
BUG=chromium:798207
TEST=test failed before; now passes
TBR=davidriley@chromium.org
Change-Id: I0f496150681cc0983dcbc7f63fab308d60ef1faa
(cherry picked from commit 7a58e83834df0b3e74e8497b0dcd92a74f06df3c)
Reviewed-on: https://chromium-review.googlesource.com/848634
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
diff --git a/scripts/merge_logs_unittest.py b/scripts/merge_logs_unittest.py
index 614a089..95a051e 100644
--- a/scripts/merge_logs_unittest.py
+++ b/scripts/merge_logs_unittest.py
@@ -41,8 +41,8 @@
# Status Log
dt = merge_logs.ParseDate('Jul 31 09:17:02')
- self.assertEqual(dt, datetime.datetime(2017, 7, 31, 9, 17, 2, 0,
- TZOFFSET))
+ self.assertEqual(dt, datetime.datetime(datetime.datetime.now().year, 7, 31,
+ 9, 17, 2, 0, TZOFFSET))
# Sysinfo
dt = merge_logs.ParseDate('2017-07-31T09:17:25.907285-07:00')
