new topics are not included in reports
Bug #658863 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-oops-tools |
Triaged
|
High
|
Unassigned |
Bug Description
we now have oops from the librarian and codebrowse, and more appservers; AIUI the OOPS reports are manually grouped.
We should instead report *all* oopses from *any* prefix in the 'lpnet' summary - its fine to have other more focused summaries, but we should have a catchall that:
- gets everything
- folk interested in overall status can look at.
Changed in launchpad-foundations: | |
status: | New → Triaged |
importance: | Undecided → High |
summary: |
- oops reports should automatically include new oops prefixes + new topics are not included in reports |
affects: | launchpad → python-oops-tools |
To post a comment you must log in.
The way I'd like to have this fixed is a complement to the fix for bug 667375. Once we eliminate the manual step needed to update summaries to find out new prefixes, we should be able to easily have a catch all summary (this bug is also related to bug 652351)