Closed Bug 837394 Opened 11 years ago Closed 11 years ago

Builds don't include Gaia commit in resources/gaia_commit.txt

Categories

(Firefox OS Graveyard :: GonkIntegration, defect)

ARM
Gonk (Firefox OS)
defect
Not set
major

Tracking

(blocking-b2g:-)

RESOLVED FIXED
blocking-b2g -

People

(Reporter: davehunt, Unassigned)

References

Details

The automation submits results with the associated Gaia commit. Builds downloaded from pvtbuilds.mozilla.org are failing due the the Gaia commit not being present.

Steps to replicate:
Flash with a unagi-eng build from pvtbuilds (https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi-eng)
adb pull /data/local/webapps/settings.gaiamobile.org/application.zip
unzip application.zip
cat application/resources/gaia_commit.txt

Expected: First line of output is Gaia commit

Actual: "Unknown Git commit; build date shown here."

See also: http://qa-selenium.mv.mozilla.com:8080/view/B2G/job/b2g.unagi.gaia.nightly.ui/217/console (requires Mozilla-MV VPN)
blocking-b2g: --- → tef?
This is not a release blocker - it's on eng builds and internal automation affecting only.
blocking-b2g: tef? → -
Dave, we still need this, right?
It prevents us running automation against the builds on pvtbuilds, so yes, we still need a way to derive the Gaia commit.
Blocks: 840797
Aki or Ben, is this something you could look at?  Thx.
I think this should have been fixed as of yesterday's nightlies.
Are you still seeing this?
Yes, this does appear to be fixed. Thanks!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.