Memory errors in unit tests under valgrind on armhf

[Alexandros Frantzis]

The Mir unit tests fail under valgrind on armhf because of spurious memory errors, most likely caused by external (to Mir) code (the dynamic linker, as an example). We aren't getting failures in CI currently, because we are ignoring valgrind errors on android.

An MP that changes this (among other things it does related to platform) is blocked by this issue. The short term solution is to disable running the tests under valgrind for armhf in CI, but it's imperative that we take care of the issue properly.

[Alexandros Frantzis (afrantzis)]

Note that this is not the same as bug 1279438 which refers specifically to memory leaks (which we aren't catching in CI at all on any platform).

[Daniel van Vugt (vanvugt)]

Using:
   valgrind --trace-children=yes bin/mir_unit_tests
on Nexus 10 I can't reproduce any failures:

   [==========] 833 tests from 142 test cases ran. (116502 ms total)
   [ PASSED ] 833 tests.

But the valgrind summary is not good:

    ==4714== ERROR SUMMARY: 1117583 errors from 582 contexts (suppressed: 200679 from 160)

That said, most of it appears to be unrelated to Mir code. Can you provide more details of what's failing?

[Alexandros Frantzis (afrantzis)]

> Using: valgrind --trace-children=yes bin/mir_unit_tests on Nexus 10 I can't reproduce any failures:

Sorry, I wasn't clear: the individual unit tests themselves don't fail, but the tests as a whole fail when run under valgrind because of the memory errors (i.e. valgrind --error-exitcode=1 ... returns 1).

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:mir/devel at revision 1419, scheduled for release in mir, milestone Unknown

[Daniel van Vugt (vanvugt)]

This bug was fixed in the package mir - 0.1.6+14.04.20140310-0ubuntu1
---------------
mir (0.1.6+14.04.20140310-0ubuntu1) trusty; urgency=medium