Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/4821#issuecomment-76821354
> flakiness of FsHistoryProviderSuite
Do you have any theories for why this would be related to the log's
modification time? The only place where it's used in FsHistoryProvider is for
filtering entries in `checkForLogs`, and it's already a conservative check (it
uses `>=` so that it picks up any new logs that show up with the same mod time
as the last check, at the expense of re-parsing logs that haven't changed).
---
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]
