tree 67bb797315bcb57576ce5e0296b4a37e50064a28
parent 1752703158a84e0f52ef13588cbf97dde92d5c81
author Daniel Erat <derat@chromium.org> 1514807627 -0800
committer ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> 1514999699 +0000

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>