Store the grammars and config file used nearby the test results. Remove valueless RQG logs.
1. A bughunt.pl run stores it's results in <storage_
The testing grammar (-> grammar), the object creation
grammar (-> gendata) and any config file (-> config) must be also
stored (as sql.yy, data.zz, run.cfg) within this directory.
sql.yy and data.zz must be used as parameters when calling runall.pl.
Hereby we can avoid a lot complications which arise if the original
files get accidently modified or removed (bzr pull , edit the grammars)
during the bughunt run or between bughunt run and analysis of it's results.
- The delay between bughunt run and analysis could be some
minutes till days.
- The analysis might cause that additional RQG runs with the old
grammars have to be performed.
2. RQG logs with a status code = 0 should be automatically deleted.
Their value - we can reveal that we had somewhere in history a run
with certain settings and status code = 0 - is extreme low.
But such logs could waste a lot space in filesystems.
IMHO a bughunt where we search for any status code including 0 but
some specific pattern within the log is very unlikely.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Bernt M Johnsen
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by