This code (hopefully) detects when you have a system that cannot handle Year 2038 dates (see https://en.wikipedia.org/wiki/Year_2038_problem) and skips tests that use those dates. This allows the test suite to pass on older systems that are using 32 bit epoch. It issues a noisy-ish warning recommending that you upgrade since modern hardware will have an upgrade path to fix this.
I wasn't able to easily reproduce this, so I set up a Test2::Mock to simulate the effects of a deficient system. There have been a few cpantesters results that exhibit this problem so if this doesn't work hopefully i will eventually get a result.
Also updated the test that seems to fail here, and catch the exception to help in diagnostics (test will still fail if for some reason the avoidance does not work).
This code (hopefully) detects when you have a system that cannot handle Year 2038 dates (see https://en.wikipedia.org/wiki/Year_2038_problem) and skips tests that use those dates. This allows the test suite to pass on older systems that are using 32 bit epoch. It issues a noisy-ish warning recommending that you upgrade since modern hardware will have an upgrade path to fix this.
I wasn't able to easily reproduce this, so I set up a Test2::Mock to simulate the effects of a deficient system. There have been a few cpantesters results that exhibit this problem so if this doesn't work hopefully i will eventually get a result.
Also updated the test that seems to fail here, and catch the exception to help in diagnostics (test will still fail if for some reason the avoidance does not work).