Bug 65219

Summary: [EasyHack] unit tests fail to clean up temp files
Product: LibreOffice Reporter: Michael Stahl <mst.fdo>
Component: LibreofficeAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium CC: dtardon, libreoffice, markus.mohrhard, tomas.chvatal
Version: 4.0.0.3 release   
Hardware: Other   
OS: All   
Whiteboard: EasyHack DifficultyBeginner SkillCpp
i915 platform: i915 features:

Description Michael Stahl 2013-05-31 17:20:32 UTC
apparently some of the tests that run during the build leave files in /tmp that they really should delete.

somebody should find out which tests are responsible for that and which cleanup function needs to be called.
Comment 1 Michael Stahl 2013-05-31 17:22:46 UTC
to narrow down the culprits build individual modules, then comment out some of the CppunitTests in Module_*.mk and finally investigate the source of the tests that are responsible (look at the CppunitTest_*.mk files to find the cxx source files).
Comment 2 Markus Mohrhard 2013-06-27 18:16:31 UTC
Miklos fixed already a large number of these leaked files during the hackfest:

http://cgit.freedesktop.org/libreoffice/core/commit/?id=c03a1e46460e4255d7709df9ba8147947f66acfb
Comment 3 Björn Michaelsen 2013-10-04 18:48:10 UTC
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.

see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Comment 4 Jass 2014-08-24 02:59:59 UTC
I am interested in working on this. I am a beginner in C++ (university student) and new to LibreOffice, and open source in general. Is there a primary contact I can reach out to if I need some pointers/help?

Thanks a lot!
Comment 5 David Tardon 2014-08-24 08:14:32 UTC
(In reply to comment #4)
> Is there a primary contact I can reach out to if I need some pointers/help?

The best way is to ask on IRC: #libreoffice-dev on FreeNode.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.