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 datetime.datetime.now 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
Reviewed-by: Dan Erat <firstname.lastname@example.org>
Tested-by: Dan Erat <email@example.com>
(cherry picked from commit 7a58e83834df0b3e74e8497b0dcd92a74f06df3c)
Reviewed-by: Bernie Thompson <firstname.lastname@example.org>
Commit-Queue: Bernie Thompson <email@example.com>
Tested-by: Bernie Thompson <firstname.lastname@example.org>
1 file changed