Increase android x86 7.0 emulator's data partition size, for gtest
Categories
(Firefox for Android Graveyard :: Testing, task)
Tracking
(firefox68 fixed)
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: gbrown, Assigned: aerickson)
References
Details
Attachments
(1 file)
We recently added support for mach gtest
on Android, which needs to install the very large gtest libxul.so on /data. That was working well with the x86 7.0 emulator just a few days ago, but today I'm running out of space on /data pretty consistently.
Let's increase the size of the /data partitions in the avd.
Reporter | ||
Comment 1•5 years ago
|
||
We increased partition sizes in bug 1519588 earlier this year. https://bugzilla.mozilla.org/show_bug.cgi?id=1519588#c5 says the x86 and 4.3 emulators are maxed out, so let's just update the x86 7.0 avd.
Partition size can be updated by simply changing the config.ini file in the avd. Let's go big! This worked for me locally:
disk.dataPartition.size=3500M
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Pushed by gbrown@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/06ead1ed1ba4 Increase android x86 7.0 emulator's data partition size r=gbrown
Comment 4•5 years ago
|
||
bugherder |
Comment 5•5 years ago
|
||
I run into the same issue right now and changing disk.dataPartition.size works fine (thanks to :gbrown). But I am wondering why my local emulator image still uses the old value? I guess that's because the local image created before landing this?
Reporter | ||
Comment 6•5 years ago
|
||
(In reply to Hiroyuki Ikezoe (:hiro) from comment #5)
I guess that's because the local image created before landing this?
Yes, that's probably the issue. You can get a new local image by run mach android-emulator with the --force-update option. Be aware that your existing image - with any installed apps or whatever - will be deleted.
Comment 7•5 years ago
|
||
Thanks for the info! I didn't notice the --force-update option at all.
Updated•3 years ago
|
Description
•