we currently run linux32 mochitest-media tests for linux32. For buildbot these are run on AWS VM instances successfully. In trying to get these running in taskcluster, we have issues: https://treeherder.mozilla.org/#/jobs?repo=try&revision=0fc2ae047976bf8990f41a0c6fcdaac9f1bffcef&filter-searchStr=media&selectedJob=32795973 what we have is the linux64 docker image with i386 libraries installed and firefox 32 bit build running. It seems as though the media tools/codecs are not installed and despite some hackery attempts we were unable to get them installed (or at least working from the point of view for firefox). I would like to determine if: a) we need to run mochitest-media jobs for linux32 (really low market share) b) if not a), then how we can run/setup the 32 bit media tools on a linux64 docker image to work with firefox.

Checking on this again, I notice differences between bb/tc in gstreamer packages. I'll try to get those re-aligned and retry the tests.

(In reply to Geoff Brown [:gbrown] from comment #1) > Checking on this again, I notice differences between bb/tc in gstreamer > packages. I'll try to get those re-aligned and retry the tests. We have no need for gstreamer since Firefox 43 (which was then only used to play MP3) All we need is a recent version of FFmpeg's libavcodec and libavutil

If it is ok, I'm going to move this to testing/general, as we usually keep core::audio/video for untriaged bugs, and it's hard to triage this elsewhere in media as it impacts both playback and webrtc.

(In reply to Jean-Yves Avenard [:jya] from comment #2) > All we need is a recent version of FFmpeg's libavcodec and libavutil Thanks! I found that adding libavcodec-ffmpeg-extra56:i386 to our 16.04 image turns the job green - yeah!

ok, this is all good and most of the w-p-t failures are fixed as well.