On the Buildbot side (bug 1220658) we upgraded to mesa-lts-saucy-9.2.1 and that caused a lot of
test failures accross the board.
In this change we're reverting upgrading to that version and going back to where we were.
--HG--
extra : commitid : KOsFpMsYfLJ
extra : rebase_source : 20c6c7f7eb1f14d256be597c25e8ac3431e7ecfb
Also calls `dpkg-reconfigure locales`, but it's not entirely clear if this is
necessary or not.
--HG--
extra : commitid : 4jWDfNVFuD0
extra : rebase_source : 926488fe6f619c9c8ae361925256fe069638e51c
This generally makes the approach look more like that for desktop-build. The
major difference is that `bin/test.sh` takes arguments which are passed on to
the mzoharness script (MOZHARNESS_SCRIPT) with the addition of config
arguments (MOZHARNESS_CONFIG)
--HG--
rename : testing/docker/desktop-build/bin/build.sh => testing/docker/desktop-test/bin/test.sh
rename : testing/docker/desktop-test/mozharness_configs/remove_executables.py => testing/mozharness/remove_executables.py
extra : commitid : GyMeTBpCwm8
extra : rebase_source : 1a61f9bc32066ad6f9fce504d3e8ac67e39b105d
This also refactors the image generation to not depend on puppetagain, and to
install the latest and greatest mercurial in a verified, repeatable way.
As with centos6-build-upd, the ubuntu1204-test-upd image exists to run
'apt-get upgrade' periodically without regenerating the huge parent image.
--HG--
extra : commitid : HxYSFfIaEc
extra : rebase_source : 28dae0a30be3d6fae2c44a43601bbd336d9bbfdd
