Need to switch CI to desktop VMs

RESOLVED FIXED

Status

Firefox OS
General
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: jgriffin, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
The B2G CI is currently running on headless linux Amazon VM's.  The tests are run by passing the --no-window argument to the emulators.

This has worked in the past, but does no longer:  running emulators with --no-window now results in a crash of the emulator (not the B2G process within the emulator) soon after the tests start.

Presumably, this is related to the work on hardware acceleration, and we should move our testing to desktop VM's.  It's unclear whether we need a real GPU as well.

We should experiement with one of the rel-eng Amazon VMs (which I believe is running Ubuntu) and see if our tests can run in that environment.  If they can, we can either utilize rel-eng VM's and/or have our existing Amazon VM's removed and replaced with similar configurations.

John, can you give us 1 such VM to experiment with?

It's possible that we will need a real GPU (which isn't available on a standard Amazon VM), and will thus need a different solution.
the VMs we've currently got running are headless centos6 boxes. we could look at running with a virtual X server (like bug 772579).
(Reporter)

Comment 2

6 years ago
(In reply to Chris AtLee [:catlee] from comment #1)
> the VMs we've currently got running are headless centos6 boxes. we could
> look at running with a virtual X server (like bug 772579).

I'll experiment locally with running the emulator with xvfb.  I have a feeling this might produce the same result as the -no-window option.
(Reporter)

Comment 3

6 years ago
(In reply to Jonathan Griffin (:jgriffin) from comment #2)
> (In reply to Chris AtLee [:catlee] from comment #1)
> > the VMs we've currently got running are headless centos6 boxes. we could
> > look at running with a virtual X server (like bug 772579).
> 
> I'll experiment locally with running the emulator with xvfb.  I have a
> feeling this might produce the same result as the -no-window option.

Selenium Android docs say:

"X compatibility

Note: The android emulator is not compatible with xvfb, and will not run in it. If you need a headless X environment, run your emulator with the -no-window option, or use tightvncserver. "
(Reporter)

Comment 4

6 years ago
I can confirm that the emulator does not work with Xvfb.  It actually ignores it, and the DISPLAY variable, and always connects to the primary physical display.
(Reporter)

Comment 5

6 years ago
I've set up an Ubuntu 11.0 desktop VM @ Amazon and will see if I can get the emulator tests working in that environment.
(Reporter)

Comment 6

6 years ago
(In reply to Jonathan Griffin (:jgriffin) from comment #5)
> I've set up an Ubuntu 11.0 desktop VM @ Amazon and will see if I can get the
> emulator tests working in that environment.

This doesn't work, emulator reports:

I/Gecko   (  104): Logging GL tracing output to /system/b2g/firefox.trace
I/Gecko   (  104): Attempting load of /data/local/egltrace.so
I/Gecko   (  104): Attempting load of libEGL.so
D/libEGL  (  104): Emulator without GPU support detected. Fallback to software renderer.
D/libEGL  (  104): loaded /system/lib/egl/libGLES_android.so
I/Gecko   (  104): Failed to create EGL config!
I/Gecko   (  104): ###!!! ABORT: failed to construct LayersChild: file /data/jenkins/jobs/b2g-build/workspace/widget/xpwidgets/nsBaseWidget.cpp, line 901
F/libc    (  104): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/DEBUG   (  103): debuggerd committing suicide to free the zombie!

This was run on an emulator with -gpu on.  Apparently, we will either need to run these tests on hardware with real GPUs, or engineering will have to fix the bugs that prevent the emulator from running with software rendering.
(Reporter)

Comment 7

6 years ago
We have switched to a new set of Ubuntu 12.04 VM's provided by rel-eng, all is running w/ no problems.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.