-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time set incorrectly in Node 12 #276
Comments
Thanks. I'm testing on OSX, but I'll try tonight on Linux and see if I get a different result. It looks like that change you highlight is the issue. 12.9.0 works fine, but not 12.10.0 (or the latest 12.11.1). |
Same problem on Ubuntu 18.04.3 LTS, with Node 12.10.0. |
Fix published in |
taneliang
added a commit
to nusmodifications/nusmods
that referenced
this issue
Mar 3, 2020
mtimeMs was returing nanoseconds instead of milliseconds. See: tschaub/mock-fs#276
ZhangYiJiang
pushed a commit
to nusmodifications/nusmods
that referenced
this issue
Mar 3, 2020
* Update CI to use Node 12 Our Docker setup already uses Node 12. * Upgrade mock-fs dep to fix one test failure mtimeMs was returing nanoseconds instead of milliseconds. See: tschaub/mock-fs#276 * Fix nus-api concurrency test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I use Node 10, I don't encounter any issues. But using Node 12 (specifically 12.10.0), the file times aren't being set correctly.
If I create a file like this:
fs.stat returns 31 Aug, 51738 for the atime and mtime, and invalid for ctime.
Explicitly setting the atime, ctime, mtime and birthtime has not effect, and produces a similar result.
The text was updated successfully, but these errors were encountered: