| Summary: | Files are modified in the future | ||
|---|---|---|---|
| Product: | Community | Reporter: | Thomas Hallgren <thomas> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Thomas Hallgren
I see this all the time when I compile a kernel on an NFS-mounted filesystem. It's usually 0.2s in the future, or something to that effect. All our servers are time-synced with an external source, and the hudson servers are using ntp which should account for clock skew and jitter, but it's by no means accurate to the 1/10th of a second. Not much I can do here other than suggest you ignore the warnings, or don't build on the master (which has its job definitions on an NFS-mounted filesystem). |