CrashKill/StabilityWeek2013/Actions: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 195: Line 195:
| New B2G Socorro Features  
| New B2G Socorro Features  
| bajaj
| bajaj
| checklist item for channel to be release-
| checklist item for channel to be release-*
|  
|  
| ?
| ?
Line 224: Line 224:
|-
|-
| B2G Stability Requirements   
| B2G Stability Requirements   
|  
| [Socorro]
| expose system app URLs publicly
| expose system app URLs publicly
| {{bug|915397}}
| {{bug|915397}}
Line 230: Line 230:
|-
|-
| B2G Stability Requirements   
| B2G Stability Requirements   
|  
| [Socorro]
| reports per-device
| reports per-device
| {{bug|853455}}
| {{bug|853455}}
Line 236: Line 236:
|-
|-
| B2G Stability Requirements   
| B2G Stability Requirements   
|  
| [Socorro]
| report by OS version 1.1.*, 1.1.2, etc.
| report by OS version 1.1.*, 1.1.2, etc.
|  
| {{bug|832362}}
| NEEDS BUG [Socorro]
| filed
|-
|-
| B2G Stability Requirements   
| B2G Stability Requirements   
Line 320: Line 320:
|-
|-
| Meet with B2G Engineering working on Crashes
| Meet with B2G Engineering working on Crashes
| KaiRo/jlebar
| KaiRo to file / jlebar
| foreground applications that go out of memory should be found
| foreground applications that go out of memory should be found
|  
| {{bug|915407}}
| ?
| filed
|-
|-
| Meet with B2G Engineering working on Crashes
| Meet with B2G Engineering working on Crashes
Line 395: Line 395:
| Annotate that the slow script dialog came up
| Annotate that the slow script dialog came up
| {{bug|907993}}
| {{bug|907993}}
| ?
| filed
|-
|-
| OOM/EMPTY crashes  
| OOM/EMPTY crashes  
Line 407: Line 407:
| Talk to jjensen about what crash data we can put in FHR, bug is leading up to this
| Talk to jjensen about what crash data we can put in FHR, bug is leading up to this
| {{bug|875562}}
| {{bug|875562}}
| ?
| gps has etherpad notes (see bug)
|-
|-
| OOM/EMPTY crashes  
| OOM/EMPTY crashes  
Line 413: Line 413:
| summarized info on gfx chipset and driver, memory, hardware/cpu
| summarized info on gfx chipset and driver, memory, hardware/cpu
| {{bug|853468}}
| {{bug|853468}}
| ?
| FIXED
|-
|-
| OOM/EMPTY crashes  
| OOM/EMPTY crashes  
| kairo to file
| kairo to file
| Annotate/show events like Firefox or MS releases on the crash charts? SUMO already has the ability to note "events" on their graphs. They use it for releases as well. Maybe we can steal or learn.
| Annotate/show events like Firefox or MS releases on the crash charts? SUMO already has the ability to note "events" on their graphs. They use it for releases as well. Maybe we can steal or learn.
|  
| {{bug|915438}}
| ?
| noted in bug
|-
|-
| OOM/EMPTY crashes  
| OOM/EMPTY crashes  
Line 460: Line 460:
| KaiRo
| KaiRo
| Ease routine jobs of putting ranks into bugs and updating topcrash keyword
| Ease routine jobs of putting ranks into bugs and updating topcrash keyword
| {{bug|913437}}
| {{bug|snorkel}}
| ?
| filed
|-
|-
| Automated Stability  
| Automated Stability  
Line 467: Line 467:
| Get a service on Socorro that will give current ranks of a signature on current releases
| Get a service on Socorro that will give current ranks of a signature on current releases
| {{bug|915373}}
| {{bug|915373}}
| ?
| filed; prototyped by bsmedberg
|-
|-
| bsmedberg hour  
| bsmedberg hour  
Line 542: Line 542:
|-
|-
| JS Engineering  
| JS Engineering  
|  
| [Socorro]
| Enable search results to be split by custom criteria (e.g. addresses) instead of signature
| Enable search results to be split by custom criteria (e.g. addresses) instead of signature
|  
|  
Line 548: Line 548:
|-
|-
| JS Engineering  
| JS Engineering  
| bsmedberg working that out with nbp
| bsmedberg/nbp
| Better way of classification for JIT crashes
| Better way of classification for JIT crashes
|  
|  
Line 557: Line 557:
| Do something (in Socorro UI) with "interesting" addresses (mark them?)
| Do something (in Socorro UI) with "interesting" addresses (mark them?)
| {{bug|918101}}
| {{bug|918101}}
| ?
| filed
|-
|-
| JS Engineering  
| JS Engineering  
Line 567: Line 567:
| JS Engineering  
| JS Engineering  
| Socorro
| Socorro
| exploitable crashes could be marked differently, see notes for heuristics
| exploitable crashes could be marked differently, see [[CrashKill/StabilityWeek2013#JS_Engineering|notes]] for heuristics
|  
|  
| ?
| ?
Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083

edits

Navigation menu