Should generate report even when there are no oopses
Bug #1014743 reported by
James Westby
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-oops-tools |
Triaged
|
Low
|
Unassigned |
Bug Description
Hi,
If a report has no oopses for a particular date then no oops report is generated on
disk, so you get a 404. That's confusing until you know why it is, and risks confusion
between "no report yet" and "no oopses".
If there are no oopses then a report should be generated that states that so there is
no confusion.
Thanks,
James
To post a comment you must log in.