Closed Bug 834585 Opened 11 years ago Closed 11 years ago

dumpless crashes left hanging in filesystem

Categories

(Socorro :: Backend, task)

Product:
Socorro
Component:
Backend
Platform:
x86_64
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: lars, Unassigned)

Details

the old (pre multidump) file system code would refuse to even save a crash if there was no dump associated with it.  The multidump code has no trouble saving crashes that have no associated dump.  Unfortunately, the filesystem walker that discovers new crashes also ignores crashes with no dumps.  This means that these crashes are never removed from the file system and passed on for further processing.  

Solution: remove the code that actually discovers the missing dump and then intentionally derails the movement of the crash.  See .../socorro/external/filesystem/json_dump_storage.py:335-339
this is no longer an issue with the new file system implementation
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.