1235898 - browser_880164_customization_context_menus.js hands when running on a docker container in task cluster

Status: RESOLVED WORKSFORME

(Firefox :: Toolbars and Customization, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

the new taskcluster environment is pretty rad, except when trying to get an image up and running with all tests passing.

We get closer every week to green tests, but we still have issues, here is an issue in browser-chrome: browser/components/customizableui/test/browser_880164_customization_context_menus.js.  We actually get stuck at yield shownPromise here:
https://dxr.mozilla.org/mozilla-central/source/browser/components/customizableui/test/browser_880164_customization_context_menus.js#209

you can see the logs here:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=1d8d18bab88b&group_state=expanded&selectedJob=14958953&filter-searchStr=bc3

and you can reproduce this fairly easily by following instructions in the inspect task (there is a shell script that will reproduce on linux if you add in some magic v4l2loopback modprobe hacks and --device args to docker run).  

Anyway, I looked at this for a while and found that line 209 is where we hang.  I run this locally on my linux64 desktop and it works fine, but inside the docker container (and possibly the different gnome-shell window manager or other settings) yield an internal timeout from the browser-chrome harness.

ideally this is something we can figure out and there is a root cause to solve the dozen or so test case timeouts we see.  Worse case scenario we can figure this out and fix this one case.

Comment 1

[:Gijs (out for now; he/him)]

I don't know anything about docker and it will take me a day+ to get this set up.

First things first: have you visually verified that the popup is actually popping up? That seems like a simple thing to start with in terms of diagnosing this.

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

I am unclear of what I am looking for, but I do see it open up the customization window via vnc and it looks very similar to what  Isee on my local desktop.  There could be some small detail I am overlooking, but at least it appears we are doing the basics.

ping me on irc and I can help with running this- it isn't too bad.  you do need a linux system to run docker though.

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

odd, in my latest push this didn't reproduce- I only filed this as I could reproduce it locally- let me hack some more on this

Comment 4

[:Gijs (out for now; he/him)]

(In reply to Joel Maher (:jmaher) from comment #2)
> I am unclear of what I am looking for, but I do see it open up the
> customization window via vnc and it looks very similar to what  Isee on my
> local desktop.  There could be some small detail I am overlooking, but at
> least it appears we are doing the basics.

It's supposed to show the context menu of the home button inside customization menu. I expect the context menu isn't showing up (for whatever reason).

> ping me on irc and I can help with running this- it isn't too bad.  you do
> need a linux system to run docker though.

I don't have a physical linux system, and running docker inside a VM sounds like a bad idea.

Comment 5

[Armen [:armenzg]]

Switching from m3.large instances to m1.medium has cleared this issue.
If any other changes bring this back up we will re-open it.