Opened 15 years ago
Last modified 15 years ago
#542 new defect
Only one summarizer per category
Reported by: | mpotter@… | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 0.6.1 |
Component: | General | Version: | 0.6b2 |
Keywords: | Cc: | mpotter@… | |
Operating System: |
Description
While attempting to write a Lint-Detail report I bumped into an issue. If there is more than one report for a given category, only one of the reports will appear. From code reading this appears to also be true for charts.
Attachments (0)
Change History (2)
comment:1 follow-up: ↓ 2 Changed 15 years ago by osimons
comment:2 in reply to: ↑ 1 Changed 15 years ago by mpotter@…
- Summary changed from Only one report per category to Only one summarizer per category
Replying to osimons:
Correct - in the same step.
I think we have a terminology overload problem. I am not referring to multiple XML reports of the same category, I am referring to multiple summarizers for the same category. In the specific case I had the standard lint summarizer and I was trying to add a lint-detail-summarizer which presented the same data in a different manner; this effort for #507.
Correct - in the same step. If you do your reports in separate steps they should all work as expected. This issue has been reported before, but that was a Postgres error iirc that had to do with Bitten trying to insert a new record with same database key(s) that already existed. Can't remember ticket number though, but something with report not being unique.
Not sure if we should redo Bitten to support it, or just improve documentation + perhaps catch the error on the master so that it for instance throws a descriptive error to the slave that says that "a report of category 'lint' already exists for this build step" or similar.
Ideas? Comments? What is needed?