|
|
| Line 1: |
Line 1: |
| | '''Project Uptime ran from April 2016 to June 2017.''' |
| | ''Preventing and fixing crashes remains an important task, and there is ongoing work there. But this work is no longer being coordinated under Project Uptime. This page is being kept in place as a historical record.'' |
| | |
| Project Uptime's goal is to reduce the crash rate of Firefox (desktop and mobile) and keep it down. This project is a Platform Engineering initiative that aims to extend and complement existing work relating to stability within Mozilla. | | Project Uptime's goal is to reduce the crash rate of Firefox (desktop and mobile) and keep it down. This project is a Platform Engineering initiative that aims to extend and complement existing work relating to stability within Mozilla. |
|
| |
|
| Line 447: |
Line 450: |
| = Nightly crash triage = | | = Nightly crash triage = |
|
| |
|
| We aim to analyze the crashes for every Nightly build.
| | This documentation has been moved to [[NightlyCrashAnalysis]]. |
| | |
| == Roster ==
| |
| | |
| Nightly builds are produced at 3am each day (California time).
| |
| | |
| * Monday (Australian time): njn analyzes Friday's build.
| |
| * Monday (US East time): marcia analyzes Saturday's build.
| |
| * Tuesday (Taiwan time): ting analyzes Sunday's build.
| |
| * Wednesday (Taiwan time): kanru analyzes Monday's build.
| |
| * Wednesday (US East time): jchen analyzes Tuesday's build.
| |
| * Thursday (US West time): mccr8 analyzes Wednesday's build.
| |
| * Friday (German time): jseward analyzes Thursday's build.
| |
| | |
| A [https://calendar.google.com/calendar/b/1/embed?src=mozilla.com_37e791c3iohijr18mi02l0dvi0@group.calendar.google.com&ctz=America/Los_Angeles live calendar] is also available for Mozilla employees. Please use it to schedule deviations from the usual roster, e.g. for PTO.
| |
| | |
| == Notes ==
| |
| | |
| Triage notes are kept in the following pages.
| |
| | |
| * [[Platform/Uptime/NightlyCrashTriage/2017Q3|2017 Q3]]
| |
| * [[Platform/Uptime/NightlyCrashTriage/2017Q2|2017 Q2]]
| |
| * [[Platform/Uptime/NightlyCrashTriage/2017Q1|2017 Q1]]
| |
| * [[Platform/Uptime/NightlyCrashTriage/2016Q4|2016 Q4]]
| |
| * [[Platform/Uptime/NightlyCrashTriage/2016Q3|2016 Q3]]
| |
| * [[Platform/Uptime/NightlyCrashTriage/2016Q2|2016 Q2]]
| |
| | |
| Use the date you are doing the triage, rather than the date of the build, to decide which page to put your notes in. The reason for this is that the triage date has a heading, which makes it more prominent in the notes than the build date.
| |
| | |
| == Data sources, tools, documentation ==
| |
| | |
| Crucial links
| |
| * [http://dbaron.org/mozilla/crashes-by-build Nightly and Aurora crashes by build]
| |
| | |
| Other links
| |
| * {{ReleaseCrashQueriesWithE10sCohorts|51.0b6|2016-12-02}}
| |
| * [https://crash-stats.mozilla.com/search/?product=Firefox&_facets=moz_crash_reason&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=moz_crash_reason#facet-moz_crash_reason All MOZ_CRASH] crashes.
| |
| * [http://bsmedberg.github.io/socorro-toolbox/html/multiple-minidumps.html Display stacks from multi-dump hangs/crashes]
| |
| * [https://crash-analysis.mozilla.com/crash_analysis/ The old, busted correlation reports]
| |
| | |
| Documentation
| |
| * A [[Platform/Uptime/NightlyCrashAnalysis|rough guide to Nightly crash analysis]]
| |
| * [https://developer.mozilla.org/en-US/docs/Understanding_crash_reports Understanding crash reports]
| |
| * [https://developer.mozilla.org/en-US/docs/A_guide_to_searching_crash_reports A guide to searching crash reports]
| |