Comment 3 for bug 1220443

What was happening was that (under android only) the test framework was being started with a stubbed graphics platform server side, but the client side was attempting to use the actual android drivers. When it went to apply the fake data from the server to the drivers, this generated a lot of errors.

The correction (in lp:~kdub/mir/fix-1220443 ) lets us put a stub client platform into our tests that run under our framework.

Why was this not seen previously?

The linking structure for these two tests was fragile. Prior to some CMakeList changes, this was not a problem because the mock android HAL was linked into the tests. Something in the link structure changed, and the linker started picking up the links to the actual drivers, causing problems. The solution should be more robust because it puts stubs in on the client side