chromite: Fix ParseDateTest.testBasicFunctionality for 2018.

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 calls. That's unlikely to happen,
but the right fix is probably to make ParseDate also take
the current time.

TEST=test failed before; now passes

Change-Id: I0f496150681cc0983dcbc7f63fab308d60ef1faa
Reviewed-by: Dan Erat <>
Tested-by: Dan Erat <>
(cherry picked from commit 7a58e83834df0b3e74e8497b0dcd92a74f06df3c)
Reviewed-by: Bernie Thompson <>
Commit-Queue: Bernie Thompson <>
Tested-by: Bernie Thompson <>
1 file changed