** Changed in: mir
Status: Fix Committed => Fix Released
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1402160
Title:
Leaks in death tests can cause subsequent tests in the same process to
fail
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
Fix Released
Bug description:
To reproduce:
valgrind --error-exitcode=1 --trace-children=yes --leak-check=full
--show-leak-kinds=definite --errors-for-leak-kinds=definite
bin/mir_acceptance_tests
--gtest_filter=ClientLibraryErrorsDeathTest*:ClientLibraryThread*
The ClientLibraryThread tests should pass and not report any definite
leaks. It's expected to get leaks from the DeathTests.
Note that for me (and Daniel, see [1]), this is still a problem even
with Christopher's fix ([2]). So, this is a real issue, just not the
one that was blocking CI.
I don't know why on some setups (e.g. Alan's) this fix seems to have
no effect. Perhaps it was a combination of this leak and the one fixed
by Chris that complicated the situation, and now that the other leak
is fixed this will work properly on all setups.
[1]
https://code.launchpad.net/~raof/mir/fix-all-the-CI/+merge/244526/comments/603009
[2] https://code.launchpad.net/~raof/mir/fix-all-the-CI/+merge/244526
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1402160/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
