Closed
Bug 851049
Opened 12 years ago
Closed 12 years ago
Need GAIA_OPTIMIZE=1 exported for all b2g builds
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: julienw, Assigned: mozilla)
Details
Attachments
(1 file)
(deleted),
patch
|
catlee
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #841886 +++
Original bug :
Vivien recently made some changes to Gaia for perf tests that are exposed to eng builds only when GAIA_OPTIMIZE=1. I've already made this change to builds produced by releases.m.c, but we want to transition away from those builds to the releng ones.
In order to do so, the unagi_eng build job will have to be changed to export GAIA_OPTIMIZE=1.
---------------------
As I stated in Bug 841886 comment 4, GAIA_OPTIMIZE=1 is only used when we trigger the build with either |make dogfood| or |make production|. This is my understanding that releng builds are not using these goals, and as a result are not optimized.
I verified this with latest builds on pvtbuilds: eng build are optimized, yet sadly non-eng builds are not optimized (mount system.img, go to b2g/system/webapps/email.gaiamobile.org, open application.zip, verify there is a "gaia_build_index.js" at the archive root).
Note that all v1.0.1 builds will get this optimization without using the env variable because we didn't uplift the env variable switch to this branch.
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → aki
Assignee | ||
Comment 1•12 years ago
|
||
I already got releng-eng.py in bug 841886.
Attachment #726266 -
Flags: review?(catlee)
Updated•12 years ago
|
Attachment #726266 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 2•12 years ago
|
||
Comment on attachment 726266 [details] [diff] [review]
GAIA_OPTIMIZE=1 for non-eng builds
http://hg.mozilla.org/build/mozharness/rev/fd8d59703252
Merged to production.
Attachment #726266 -
Flags: checked-in+
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•