I moved back to confirmed, and will link in specific issues to this bug. After we get --track-fds = yes to produce clean output, we'll turn it on that flag in our valgrind runs.
-- 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/1353961 Title: Mir test code (and possibly production code) leaks fds Status in Mir: Confirmed Status in “mir” package in Ubuntu: Fix Released Bug description: Steps to reproduce: valgrind --tool=none --track-fds=yes mir_(unit|integration|acceptance)_tests Expected result: No fds are leaked Actual result: A lot of fds are leaked As with memory errors it's important to reach a state where we don't leak any fds in our tests. This will helps us catch fd leak regressions in production code. When we reach the zero leak state we can enable --track-fds=yes in CI. See, for example, https://bugs.launchpad.net/mir/+bug/1353461 which was caused by fd leaks both in test code and _production code_, and was lost in the fd leak noise we currently produce. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1353961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
