If a call to Date.parse or DateTime.parse passed a second or third argument while Timecop was loaded, the patched parse method would not match the arity since it was only expecting a single arg.
Eliminates these warnings: “…/lib/timecop/timecop.rb:110: warning: instance variable @safe_mode not initialized” “…lib/timecop/time_stack_item.rb:45: warning: instance variable @travel_offset not initialized” “…lib/timecop/time_stack_item.rb:49: warning: instance variable @scaling_factor not initialized” “lib/timecop/time_stack_item.rb:140: warning: mismatched indentations at 'end' with 'class' at 1” “…lib/timecop/time_extensions.rb:74: warning: method redefined; discarding old now.” For the method redefinition warning, could have used `undef :now’, but seems cleaner instead to alias :now_without_mock_time to be the old :now, rather than coding up an equivalent. (Same pattern as used in Time in the same file)
…ch unsets any global freezes or travels
On 2013-11-23, minitest-reporters released v1.0.0, which instead of relying on minitest <= 5.0, requires minitest >= 5.0. This change breaks the travis build since we rely on some deprecated APIs. This change locks us to the 0.14 series of minitest-reporters.