Closed Bug 750366 Opened 12 years ago Closed 11 years ago

[tracking bug] Start producing Android x86 Firefox builds

Categories

(Release Engineering :: General, defect, P4)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mfinkle, Assigned: kmoir)

References

Details

(Whiteboard: [android][waiting on dep bugs]) 

In an effort to become more compatible with Android running on x86 hardware, we'd like to create build-only automation. This would NOT unclude tests. To start, we'd only like to get builds. We can add tests later, as we become more active on Android x86 hardware.
Summary: Create a builder for Android x86 → Start producing Android x86 Firefox builds
Mark, breakpad doesn't work on Android/x86 (it is build error).   Should we disable it into configure.in until supporting it?
And, we need NSPR 4.9.1 for x86 build.  Current m-c is 4.9.
Component: Release Engineering → Release Engineering: Automation (General)
QA Contact: release → catlee
From channel meeting discussions yesterday this is much lower priority than other work on our plate right now - https://wiki.mozilla.org/Firefox/Channels/Meetings/2012-05-08#RelEng
Priority: -- → P4
Whiteboard: [android]
There are still a few kinks to be worked on here anyway: bug 723713
Depends on: 723713
I have done a rough patch that could work off the bat.

If one of you could land the mozconfig changes for this build I could give it a shot on staging whenever I have a change.

For reference, Android uses this:
http://hg.mozilla.org/mozilla-central/file/default/mobile/android/config/mozconfigs/android/nightly
bug 757909 is adding mozconfigs, but there are other issues that make these builds not work yet, so we'll have to fix those first.
This appears to not have used the right mozconfig:
retry: Calling <function run_with_timeout at 0xb7d450d4> with args: (['bash', '-c', 'if [ -f "mobile/android/config/mozconfigs/android/nightly" ]; then                        echo Using in-tree mozconfig;                        cp mobile/android/config/mozconfigs/android/nightly .mozconfig;                    else                        echo Downloading mozconfig;                        wget -O .mozconfig http://hg.mozilla.org/build/buildbot-configs/raw-file/production/mozilla2/android/mozilla-central/nightly/mozconfig;                    fi'], 1260, None, None, False, True), kwargs: {}, attempt #1

In any event, these builds won't work on tinderbox until we fix the bugs blocking this one.
Ok, that makes more sense. You're hitting bug 756816 there.
Assignee: nobody → armenzg
Whiteboard: [android] → [android][waiting on dep bugs]
For now I will assign myself until we're closer for me to test it.
Assignee: armenzg → nobody
Blocks: mobile-automation
per meeting w/blassey yesterday:

1) We agree this remains much lower priority then armv6 (on apc.io) or android4.0 (on pandas).

2) This bug (and dep bugs) are on hold until the higher priority projects are completed. Blassey + I will revisit this in late Oct... or sooner if all goes well.
Motorola now sells the x86 "Razr i" in Europe, which has a lot of fans for small size, good performance and reasonable price. Firefox is one of only 3 apps frequently missed (Flash/AIR, Shazam the others).
It looks like an unlocked one can be ordered here if needed in the US. http://www.expansys-usa.com/motorola-razr-i-intel-atom-android-smartphone-unlocked-237359/

There is also the Orange San Diego in Europe that has Intel in it that has a much more resonable price than the Razr i.  
http://support.mozilla.org/en-US/questions/934783

There's the Xolo in India. http://xolo.in/

There's one available from a russian carrier as well.  http://www.anandtech.com/show/6179/intels-medfield-reference-design-picked-up-by-russias-megafon
Now that the ARMv6 support is done, is it possible to start working on x86? Indeed, Motorola Razr i will be under many European Christmas trees.
We were blocked on bug 756816, which may have been fixed by the switch to our new build slaves using mock, but that change made the newer version of the NDK (required to build for x86) unavailable without further changes, so we haven't been able to test. This is very low on RelEng's list of priorities so nobody has looked at it.
I know that mobile still wants this and have loaned a mock slave to see what is needed to get this going.
Assignee: nobody → kmoir
Summary: Start producing Android x86 Firefox builds → [tracking bug] Start producing Android x86 Firefox builds
Depends on: 820592
Depends on: 820600
Depends on: 820882
I'll land the changes for this in bug 820592 + reconfig on Monday.  Today was busy deploying new pandas for Android.
Depends on: 822653
I just installed Nightly: fennec-20.0a1.multi.android-i386.apk	19-Dec-2012 13:45 	23M, and it's working well.
I consider this bug solved. Next step: Firefox on Play Store.
(In reply to Aissen from comment #20)
> I just installed Nightly: fennec-20.0a1.multi.android-i386.apk	19-Dec-2012
> 13:45 	23M, and it's working well.
> I consider this bug solved. Next step: Firefox on Play Store.

While I appreciate the enthusiasm, this is marked as a tracking bug for a reason. There are many other steps required before we're ready for the Play Store.
Can this bug be closed?  We can open a new tracking bug with the changes required to put Android x86 tests into production once the infrastructure is ready.
Per comment 0 this was only about builds, so this could have been marked FIXED a while ago.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.