-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
test-fs-utimes-y2K38 fails on 32-bit platforms with 64-bit time_t #45906
Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
Labels
fsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Description
Activity
Metadata
Metadata
Assignees
Labels
fsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Version
v18.12.1
Platform
Linux ember.foxkit.us 5.15.44-mc2-easy #1 SMP Wed Aug 17 20:37:04 UTC 2022 i686 GNU/Linux
Subsystem
fs
What steps will reproduce the bug?
make jsteston a 32-bit computer with 64-bittime_t.How often does it reproduce? Is there a required condition?
Always reproducible on any 32-bit computer with 64-bit
time_t. This includes Linux musl libc, and glibc when_TIME_BITS=64.What is the expected behavior?
Passing tests.
What do you see instead?
Additional information
This is passing on the 16 LTS branch. It seems like it may be fallout from #43714 but I'm not sure.