Community
Participate
Working Groups
Build Identifier: Monitoring-Reports can be very large and they are currently not deleted from the database. There should be a mechansim to delete reports from time to time. I've attached a patch that will fix this problem. Reproducible: Always
Created attachment 187728 [details] This patch will fix the database overfill problem with monitoring reports
Created attachment 187729 [details] new version of previous patch
Comment on attachment 187728 [details] This patch will fix the database overfill problem with monitoring reports newer version of the patch makes this one obsolete
Comment on attachment 187729 [details] new version of previous patch patch applied with http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=2c84e0f34e3550d9c3e9810abbf9304f593591a4 Thank you.
fixed with http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=2c84e0f34e3550d9c3e9810abbf9304f593591a4
I tried this on a virtual machine and create a test result summary including a monitoring report. Then I close the GUIdancer and change the date of the virtual machine to a month later. When I start the GUIdancer and open my project, in the progress window I can see a job 'Cleaning Test Results', which sleeps a time and then deletes the Test Result Summaries. But it is still possible to open a Profiling Report with the Button 'Open Profiling Report'. Also in the file system the folder for the profiling report still exists. This behavior is the same after restarting the GUIdancer.
Sorry. Successfully tested.