Hang, "Attempt to set swap interval on screencast is invalid" on ubuntuuitoolkit autopilot tests

[Allan LeSage]

While validating lp:1421009 , finding a full freeze while running ubuntu-ui-toolkit autopilot tests, seeing the following, will attach cam shot of UI.

alesage@dioptrique:~/workspace/flashing⟫ phablet-test-run ubuntuuitoolkit
Loading tests from: /usr/lib/python3/dist-packages

Tests running...
[1429739342.540908] Loader: Loading modules from: /usr/lib/arm-linux-gnueabihf/mir/client-platform/
[1429739342.542058] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so.2
[1429739342.542917] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so.2
[1429739342.544176] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
[1429739342.603784] <ERROR> mircommon: Caught exception at Mir/EGL driver boundary (in setSwapInterval): /build/buildd/mir-0.12.1+15.04.20150324/src/client/buffer_stream.cpp(283): T$
row in function virtual void mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_errorEEEE
std::exception::what: Attempt to set swap interval on screencast is invalid

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: mir-client-platform-mesa2 0.12.1+15.04.20150324-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.17.2-0ubuntu1
Architecture: armhf
Date: Wed Apr 22 22:00:20 2015
InstallationDate: Installed on 2015-04-22 (0 days ago)
InstallationMedia: Ubuntu 15.04 - armhf (20150422-020205)
SourcePackage: mir
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1425307, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.