835556 - Gaia Version no longer appears in settings correctly for b2g18 v1.0.0

Status: RESOLVED DUPLICATE of bug 834892

(Release Engineering :: General, defect)

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Attachment: screenshot

1. download the build
2. flash
3. go to settings -> device info -> more info

Expected: gaia version should be listed
Actual: gaia version is not listed.

Gecko  http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_0/rev/b30d5224b47b
Gaia   Unknown Git commit; build date shown here.
BuildID 20130128070201
Version 18.0

Note: from sources.xml : Mercurial-Information: <project name="integration/gaia-1_0_0" path="gaia" remote="hgmozillaorg" revision="2a3396c64c0a"/> -->

Comment 1

[John Ford [:jhford] CET/CEST Berlin Time]

Releng, are we no longer generating the gaia_commit_override.txt file?

Comment 2

[Aki Sasaki (not active)]

Still being generated:
http://hg.mozilla.org/build/mozharness/file/4af241ce3165/scripts/b2g_build.py#l571

Comment 3

[John Ford [:jhford] CET/CEST Berlin Time]

The makefile in v1.0.0 has the override reading logic.  Can you verify the contents of this file for an actual build?  I wonder if the Git->HG->Git revision mapping system might be causing this failure.

Comment 4

[Chris AtLee [:catlee]]

query_do_translate_hg_to_git() is probably returning False for everything except mozilla-b2g18, since we're also not publishing those manifests yet.

http://hg.mozilla.org/build/mozharness/file/4af241ce3165/scripts/b2g_build.py#l465

I think this should be cleaned up by bug 834892?

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Yes, it is.  Closing as works for me.:

Tested on : 
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/b9871d06ba06
Gaia   03401aa0cedac9bc8332e1342aac274a62f4416f
BuildID 20130129070201
Version 18.0
Unagi

Comment 6

[Aki Sasaki (not active)]

That's b2g18, not b2g18_v1_0_0.  I do think bug 834892 will fix this.

Comment 7

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

ASDFASDF.  Thanks for the catch. 

I'll just mark this as a dup of bug 834892 if you think the fix will be in there.