Fix military date parsing not adjusting date

[cerdelen]

fixes #9775.

I fixed the bug described in this issue and also added regression tests.

I am pretty sure that the unwrap i added is not okay but i am not sure what fallback date to use if the edgecases of the time is reached and would love for someone to give me some input.

[codspeed-hq]

CodSpeed Performance Report

Merging #9785 will not alter performance

_{Comparing cerdelen:fix_date_military_parsing (374d880) with main (911bc15)}

Summary

✅ 136 untouched
⏩ 24 skipped¹

Footnotes

1. 24 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[github-actions]

GNU testsuite comparison:

GNU test failed: tests/tail/retry. tests/tail/retry is passing on 'main'. Maybe you have to rebase?

[github-actions]

GNU testsuite comparison:

GNU test failed: tests/tty/tty-eof. tests/tty/tty-eof is passing on 'main'. Maybe you have to rebase?

[github-actions]

GNU testsuite comparison:

Skipping an intermittent issue tests/misc/tee (passes in this run but fails in the 'main' branch)

[github-actions]

GNU testsuite comparison:

GNU test failed: tests/sort/sort-stale-thread-mem. tests/sort/sort-stale-thread-mem is passing on 'main'. Maybe you have to rebase?
Skipping an intermittent issue tests/misc/tee (passes in this run but fails in the 'main' branch)
Note: The gnu test tests/csplit/csplit-heap is now being skipped but was previously passing.
Note: The gnu test tests/printf/printf-surprise is now being skipped but was previously passing.

[cerdelen]

also fixes #9798

[sylvestre]

@cerdelen could you please update this PR with the test cases from #9798 ?
thanks

[cerdelen]

@cerdelen could you please update this PR with the test cases from #9798 ? thanks

line 1117 in file tests/by-util/test_date.rs already tests this explicitly for correct time

and i extended my test with this variation too to checks that the date is correct

[cerdelen]

@sylvestre is the 1 failing Pipeline maybe flakey. Its some test with 'more'? So i have to investigate this failed Pipeline or is it okay?

[sylvestre]

Don't hesitate to investigate :)
In a different pr

[cerdelen]

Is there anything else needed for this PR before it can be merged into the repository?