Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335565 - Monitoring-Reports can unnecessarily overfill the database
Summary: Monitoring-Reports can unnecessarily overfill the database
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Zeb Ford-Reitz CLA
QA Contact: Tim Winselmann CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-27 08:01 EST by Marc Steffens CLA
Modified: 2011-02-23 06:45 EST (History)
2 users (show)

See Also:


Attachments
This patch will fix the database overfill problem with monitoring reports (2.08 KB, patch)
2011-01-27 08:04 EST, Marc Steffens CLA
no flags Details | Diff
new version of previous patch (2.05 KB, patch)
2011-01-27 08:45 EST, Marc Steffens CLA
zeb.ford-reitz: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Steffens CLA 2011-01-27 08:01:22 EST
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
Comment 1 Marc Steffens CLA 2011-01-27 08:04:12 EST
Created attachment 187728 [details]
This patch will fix the database overfill problem with monitoring reports
Comment 2 Marc Steffens CLA 2011-01-27 08:45:26 EST
Created attachment 187729 [details]
new version of previous patch
Comment 3 Zeb Ford-Reitz CLA 2011-01-27 08:47:54 EST
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 4 Zeb Ford-Reitz CLA 2011-01-27 08:57:54 EST
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.
Comment 6 Tim Winselmann CLA 2011-02-23 05:59:02 EST
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.
Comment 7 Tim Winselmann CLA 2011-02-23 06:45:08 EST
Sorry. Successfully tested.