Does anyone know why otherwise-sane Windows boxes—four separate installs of 2000 and XP across machines from different vendors—would advance their clocks by up to 30 seconds every 4-5 minutes? This doesn’t happen all of the time, only when they’re running builds; when the boxes are idle their clocks don’t diverge from NTP by more than a fraction of a second each day. It’s really starting to tick me off, since Tinderbox relies on its build providers having accurate time and complains loudly when someone’s out of sync. (While I was composing this post I received five e-mail notifications of unsynchronized updates.)
None of the Linux or Solaris tinderbox builders under similar load have this problem, so it’s got to be a problem with Windows itself. Maybe there’s a magic registry incantation to fix it… anyone? Please?
