guybedford edited PR #7569.
guybedford edited PR #7569:
Node.js mtime setting only works up to 100µs accuracy.
This updates the test to work at this level at minimum when the
NO_ACCURATE_TIME
option is set.
We could make this a configurable test option, I just wasn't sure how to set up such a conditional build feature for the test program - suggestions welcome if not reducing overall accuracy is preferred.
guybedford updated PR #7569.
guybedford updated PR #7569.
guybedford updated PR #7569.
guybedford edited PR #7569:
Node.js mtime setting only works up to 100µs accuracy.
This updates the test to work at this level at minimum when the
NO_ACCURATE_TIME
option is set.
We could make this a configurable test option, I just wasn't sure how to set up such a conditional build feature for the test program - suggestions welcome if not reducing overall accuracy is preferred.
guybedford edited PR #7569:
Node.js mtime setting only works up to microsecond accuracy.
This updates the test to work at this level at minimum when the
NO_ACCURATE_TIME
option is set.
We could make this a configurable test option, I just wasn't sure how to set up such a conditional build feature for the test program - suggestions welcome if not reducing overall accuracy is preferred.
guybedford submitted PR review.
guybedford created PR review comment:
Ahh I misread the documentation here that the units were 100 nanoseconds.
The actual units are therefore microsecond accuracy and this is 2 microseconds.
guybedford updated PR #7569.
guybedford edited PR #7569:
Node.js mtime setting only works up to microsecond accuracy.
This updates the test to work at this level at minimum when the
FS_TIME_PRECISION
option is set.
We could make this a configurable test option, I just wasn't sure how to set up such a conditional build feature for the test program - suggestions welcome if not reducing overall accuracy is preferred.
Last updated: Dec 23 2024 at 12:05 UTC