Closed
Bug 1045453
Opened 10 years ago
Closed 10 years ago
[dolphin] dolphin pvt build locked down to old commits
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: angelc04, Unassigned)
References
Details
I checked the latest pvt build here:
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-b2g30_v1_4-dolphin/2014/07/2014-07-28-16-02-06/
The gecko commit is on July 13th which is older than last pvt build 20140724000201. For gaia commit, I don't know how to check. But anyway, the new pvt build does not include new changes.
Please help check.
Gaia eb3b185325901d4c04e2d43eb58d90835213bea9
Gecko https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/8c8883bb5797
BuildID 20140728160206
Version 30.0
ro.build.version.incremental=314
ro.build.date=Tue Jul 22 20:54:56 CST 2014
Reporter | ||
Comment 1•10 years ago
|
||
nick, could you please help check again?
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(nthomas)
Comment 2•10 years ago
|
||
The gecko revision is OK actually.
Both git and hg record the original landing time for a changset. Whens patches are uplifted from other repos that timestamp may be preserved (eg hg transplant). You can always refer to the pushlog, ie
https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/pushloghtml?fromchange=802e5cf2834b&tochange=8c8883bb5797
to see when it actually landed in the important repo. Compare that with
https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/8c8883bb5797
I don't know of an equivalent for git.
8c8883bb5797 is the current tip of mozilla-b2g30_v1_4, and that's fresh, so --> INVALID.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(nthomas)
Resolution: --- → INVALID
Assignee | ||
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•