Firefox OS/Performance/Investigating Alerts: Difference between revisions

Jump to navigation Jump to search
Line 36: Line 36:
The last section of the alert is the details of the regression.  For the given build, there could be many regressions found, we will list all of them in this section.
The last section of the alert is the details of the regression.  For the given build, there could be many regressions found, we will list all of them in this section.


=== Device type ===
[[File:Alert_details_device.png|600px]]
[[File:Alert_details_device.png|600px]]


We outline which device model is used.  The example here is Tarako, Other values are Hamachi as well.
We outline which device model is used.  The example here is Tarako, Other values are Hamachi as well.


 
=== Suite ===
After the device we mention what suite showed a regression. In this example we have 'vsize' as the suite:
After the device we mention what suite showed a regression. In this example we have 'vsize' as the suite:
[[File:Alert_details_suite.png|600px]]
[[File:Alert_details_suite.png|600px]]
Line 50: Line 51:
** possible values are: pss, rss, system_pss, system_rss, system_uss, system_vsize, uss, vsize
** possible values are: pss, rss, system_pss, system_rss, system_uss, system_vsize, uss, vsize


=== Testname ===
Next is the testname that was run inside of the suite.  In this example we have 'email_memory':
Next is the testname that was run inside of the suite.  In this example we have 'email_memory':
[[File:Alert_details_testname.png|600px]]
[[File:Alert_details_testname.png|600px]]
Line 59: Line 61:
** possible values are: communications/contacts_memory, communications/dialer_memory, communications/ftu_memory, email_memory, settings_memory
** possible values are: communications/contacts_memory, communications/dialer_memory, communications/ftu_memory, email_memory, settings_memory


=== Datazilla links ===
The next section is the Datazilla links, these are mostly self explanatory and for more information on what the view in Datazilla means check out [[/Bisecting_Regressions|Bisecting_Regressions]]:
The next section is the Datazilla links, these are mostly self explanatory and for more information on what the view in Datazilla means check out [[/Bisecting_Regressions|Bisecting_Regressions]]:
[[File:Alert_datazilla_link.png|600px]]
[[File:Alert_datazilla_link.png|600px]]


=== Link to diff ===
After the links to Datazilla, we show a link to a diff of the Gaia repository (all changes from the previous test run to the current one):
After the links to Datazilla, we show a link to a diff of the Gaia repository (all changes from the previous test run to the current one):
[[File:Alert_github_diff.png|600px]]
[[File:Alert_github_diff.png|600px]]


=== Date of regression ===
The next field is the date.  This is the date that the results were posted to Datazilla.  Not the date we did the build or started the test run.  Not the date that we detected the regression.  Since the alerting system waits for future data, this date will be a few hours older than the email:
The next field is the date.  This is the date that the results were posted to Datazilla.  Not the date we did the build or started the test run.  Not the date that we detected the regression.  Since the alerting system waits for future data, this date will be a few hours older than the email:
[[File:Alert_details_date.png|600px]]
[[File:Alert_details_date.png|600px]]


=== Raw Numbers ===
The last section of the details is the raw numbers for Before, After, and Diff:
The last section of the details is the raw numbers for Before, After, and Diff:
[[File:Alert_details_numbers.png|600px]]
[[File:Alert_details_numbers.png|600px]]
Confirmed users
3,376

edits

Navigation menu