Closed
Bug 734001
Opened 14 years ago
Closed 14 years ago
update_reports_clean blows up on new garbage data
Categories
(Socorro :: Database, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jberkus, Assigned: jberkus)
Details
(Whiteboard: [2.5.0.1])
We're getting some rows which blow up in a new way since March 5, preventing update_reports_clean from filling in that hour of data. In the 2.5.0 release we added a fix for this, but it appears not to work in all cases. For example, somewhere in 2012-03-06 06:00 to 12:00 there's some bad rows which manage to violate a not-null constraint on OS_version.
As such, I need to investigate this, identify the bad rows, figure out why they're not being matched, and fix the issue. To be applied to prod as 2.5.0.1
| Assignee | ||
Comment 1•14 years ago
|
||
Actually, between 2012-03-06 11:00 and 12:00
| Assignee | ||
Comment 2•14 years ago
|
||
Patched as version 2.5.0.1
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•14 years ago
|
Whiteboard: [2.5.0.1]
You need to log in
before you can comment on or make changes to this bug.
Description
•