Need GAIA_OPTIMIZE=1 exported for all b2g builds



6 years ago
3 months ago


(Reporter: julienw, Assigned: aki)


Firefox Tracking Flags

(Not tracked)



(1 attachment)

+++ 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/, open, 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.
Assignee: nobody → aki

Comment 1

6 years ago
Created attachment 726266 [details] [diff] [review]
GAIA_OPTIMIZE=1 for non-eng builds

I already got in bug 841886.
Attachment #726266 - Flags: review?(catlee)


6 years ago
Attachment #726266 - Flags: review?(catlee) → review+

Comment 2

6 years ago
Comment on attachment 726266 [details] [diff] [review]
GAIA_OPTIMIZE=1 for non-eng builds
Merged to production.
Attachment #726266 - Flags: checked-in+


6 years ago
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: → Release Engineering
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.