59 bytes, text/x-review-board-request
OK. The issue here is that Taskcluster builds are done on systems based on UTC and buildbot builds are done on systems on US/Pacific time. So during the winter, taskcluster builds were designed to kick-off at the same time as the buildbot builds, but now that the buildbot builds kick off an hour earlier because of so called Daylight Saving time, they are completely out of sync. So I would like to propose that taskcluster builds be based off the state of mozilla-central at 10:02. That rationale is that by the next Daylight Saving time transition all builds will be on Taskcluster, and also that delaying the already arrive too late in US/Easter ntimezone by an additional hour in the summer is not acceptable. The current situation is that often because of the normal merge time performed by sherrifs is after the 3:02 pacific time kickoff of buildbot nightlies and the next hour is the window in which merges between central inbound autoland and fx normally occur. The corrent situation results in Widows nightly builds having more affinity to the previous days Linux builds than to the same day.
Summary: huge deviation between congests included in Linux nightly builds and same day Windows nightly builds. → huge deviation between changests included in Linux nightly builds and same day Windows nightly builds.
Comment on attachment 8852006 [details] Bug 1351306 - Move the UTC starttime of nightlies earlier. https://reviewboard.mozilla.org/r/124254/#review126804
Attachment #8852006 - Flags: review?(rail) → review+
Pushed by Callek@gmail.com: https://hg.mozilla.org/integration/autoland/rev/3a10b2084b4a Move the UTC starttime of nightlies earlier. r=rail
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.