Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3687#issuecomment-67265698
It turns out that my current use of `file.setLastModified` is brittle since
the underlying filesystem may only support one-second resolution:
```
* <p> All platforms support file-modification times to the nearest
second,
* but some provide more precision. The argument will be truncated to
fit
* the supported precision. If the operation succeeds and no
intervening
* operations on the file take place, then the next invocation of the
* <code>{@link #lastModified}</code> method will return the (possibly
* truncated) <code>time</code> argument that was passed to this method.
```
I wish there was a better way to mock the filesystem in these tests. In
the meantime, though, I could stick with batch intervals that are multiples of
seconds (since we only need to do this in two tests).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
