Oops report shows the wrong "longest statements" in OOPS-1702F648
Bug #626629 reported by
Jeroen T. Vermeulen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-oops-tools |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Look at this oops report from a daily "longest page render times" report:
OOPS-1702F648
The "longest statements" listing tops out at 35ms. Yet several queries take longer than that, including #927 which takes orders of magnitude more time.
| affects: | launchpad → oops-tools |
| Changed in oops-tools: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| affects: | oops-tools → python-oops-tools |
| description: | updated |
| summary: |
- Oops report shows the wrong "longest statements." + Oops report shows the wrong "longest statements" in OOPS-1702F648 |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| Changed in python-oops-tools: | |
| importance: | High → Low |
To post a comment you must log in.
While a bit of a worry, this is tolerable given that good pages don't have hundreds of queries :). If someone wants to work on it I'd be happy to grab a sanitised copy of the oops file.