Closed
Bug 966251
Opened 12 years ago
Closed 12 years ago
Hamachi nightly builds are not using the latest Gaia
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: zcampbell, Unassigned)
Details
The new build from today is still using the same Gaia commit as the build that came before it.
It should be picking up a newer commit.
New Taipei timezone build:
<project name="gaia.git" path="gaia" remote="mozillaorg" revision="09064f43116d1b965cb3ab6516fa0f1fa3c98a4c"/>
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-hamachi-eng/2014/01/2014-01-30-16-02-00/sources.xml
Usual PST timezone build - this one has the same Gaia commit
<project name="gaia.git" path="gaia" remote="mozillaorg" revision="09064f43116d1b965cb3ab6516fa0f1fa3c98a4c"/>
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-hamachi-eng/2014/01/2014-01-31-04-02-02/sources.xml
Comment 1•12 years ago
|
||
I think everything is working as expected here. The b2g builds have been broken since the commit to mozilla-central at 3:49am pacific. Because of that we used the prior rev5e0a22097bff (8:28pm pacific on jan 30th) for the pacific time nightly. Perhaps the confusion is that you were expecting an even more recent gecko, which would've had a newer gaia (aedd5c9636f305d4433491056a0ca984dfb859b1, for example).
Note that because sources.xml is embedded into the Gecko tree that we cannot pull a different one when we do the b2g builds. As long as the b2g builds are fixed by the next nightly, you'll get a newer gecko and gaia.
Comment 2•12 years ago
|
||
Resolving WFM because I haven't seen any evidence that the automation is broken. If necessary you can ping someone in #releng to spin an additional set of nightlies once mozilla-central's device builds are green again.
Assignee: bhearsum → nobody
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•