On Tue, 4 Jan 2022 16:46:09 GMT, Aleksey Shipilev wrote:
> The real problem is Y2038
> ([JDK-8279444](https://bugs.openjdk.java.net/browse/JDK-8279444)), which does
> not look solvable at this time. So for test cleanliness, we might just
> disable this test on 32-bit platforms.
>
> Additional
On Tue, 4 Jan 2022 16:46:09 GMT, Aleksey Shipilev wrote:
> The real problem is Y2038
> ([JDK-8279444](https://bugs.openjdk.java.net/browse/JDK-8279444)), which does
> not look solvable at this time. So for test cleanliness, we might just
> disable this test on 32-bit platforms.
>
> Additional
On Tue, 4 Jan 2022 16:46:09 GMT, Aleksey Shipilev wrote:
> The real problem is Y2038
> ([JDK-8279444](https://bugs.openjdk.java.net/browse/JDK-8279444)), which does
> not look solvable at this time. So for test cleanliness, we might just
> disable this test on 32-bit platforms.
>
> Additional
The real problem is Y2038
([JDK-8279444](https://bugs.openjdk.java.net/browse/JDK-8279444)), which does
not look solvable at this time. So for test cleanliness, we might just disable
this test on 32-bit platforms.
Additional testing:
- [x] Linux x86_64 fastdebug, affected test still passes
-