`du --time` crashes with large timestamp (`tests/du/bigtime`)

[drinkcat]

Linked to #8355. If that initial test passed, we'd hit this in tests/du/bigtime

Steps to repro (might need to use tmpfs for this, e.g. my local ext4 does not like such large timestamps)

$ touch -d @9223372036854775807 /tmp/future
$ LC_ALL=C TZ=UTC0 du --time /tmp/future
0	du: time '9223372036854775807' is out of range
9223372036854775807	/tmp/future
$ LC_ALL=C TZ=UTC0 cargo run du --time /tmp/future
thread '<unnamed>' panicked at /home/drinkcat/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/chrono-0.4.41/src/datetime/mod.rs:1856:38:
No such local time
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
du: Printing thread panicked.

So:

1. We should not crash
2. We should print dates up to @67768036191676799 (year 2147485547)

Note that the crash is in chrono here, so maybe we should switch to jiff like we did with ls (see #7852), but as seen in #8355, jiff behaviour also isn't quite what we want.

[ChrisDryden]

I can see that the test now passes and we can support not crashing for very large timestamps, but there still is a difference between GNU and UUTILS here where GNU 9.9 can handle times up to 67768036191676799 and the uutils version shows the "is out of range error message".

Not the most practical issue, but still a deviation

[sylvestre]

are you sure ?

$ LANG=C /usr/bin/du --time /tmp/future
0	du: time '67768036191676799' is out of range
67768036191676799	/tmp/future

$ cargo run --features unix -q du --time /tmp/future
du: time '67768036191676799' is out of range
0	67768036191676799	/tmp/future

(this is almost the same output, just some mix between stderr & stdout)

[ChrisDryden]

What version are you running? Maybe is a filesystem specific thing

LC_ALL=C TZ=UTC0 /usr/bin/du --time /dev/shm/future2 2>&1
#0	2147485547-12-31 23:59	/dev/shm/future2

LC_ALL=C TZ=UTC0 ~/uutils/coreutils/target/debug/du --time /dev/shm/future2 2>&1
#du: time '67768036191676799' is out of range

[sylvestre]

main on tmpfs

[ChrisDryden]

I'm going on a hunch:

LC_ALL=C TZ=Europe/Paris ~/uutils/gnu/src/du --time /dev/shm/timetest 2>&1
0	du: time '67768036191676799' is out of range

The only difference between the two commands was the TZ, can you try with UTC?