{"action":"created","issue":{"url":"https://api.github.com/repos/mozilla/telemetry-dashboard/issues/291","repository_url":"https://api.github.com/repos/mozilla/telemetry-dashboard","labels_url":"https://api.github.com/repos/mozilla/telemetry-dashboard/issues/291/labels{/name}","comments_url":"https://api.github.com/repos/mozilla/telemetry-dashboard/issues/291/comments","events_url":"https://api.github.com/repos/mozilla/telemetry-dashboard/issues/291/events","html_url":"https://github.com/mozilla/telemetry-dashboard/issues/291","id":210557998,"number":291,"title":"factor in gpu-process crashes into the crash dashboard","user":{"login":"philipp-sumo","id":1524147,"avatar_url":"https://avatars.githubusercontent.com/u/1524147?v=3","gravatar_id":"","url":"https://api.github.com/users/philipp-sumo","html_url":"https://github.com/philipp-sumo","followers_url":"https://api.github.com/users/philipp-sumo/followers","following_url":"https://api.github.com/users/philipp-sumo/following{/other_user}","gists_url":"https://api.github.com/users/philipp-sumo/gists{/gist_id}","starred_url":"https://api.github.com/users/philipp-sumo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/philipp-sumo/subscriptions","organizations_url":"https://api.github.com/users/philipp-sumo/orgs","repos_url":"https://api.github.com/users/philipp-sumo/repos","events_url":"https://api.github.com/users/philipp-sumo/events{/privacy}","received_events_url":"https://api.github.com/users/philipp-sumo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-02-27T17:52:21Z","updated_at":"2017-02-28T14:55:29Z","closed_at":null,"body":"firefox 53 introduces a new gpu process (\"quantum compositor\") - we should find a way to incorporate that into the crash dashboard. \r\n\r\nat the moment it looks like in socorro there is a rather small number of those reports, so maybe we can just count those crashes into the content crash rate (also see issue #290), as those types of crashes might feel similar to affected users, and add a note about this on the dashboard."},"comment":{"url":"https://api.github.com/repos/mozilla/telemetry-dashboard/issues/comments/283060736","html_url":"https://github.com/mozilla/telemetry-dashboard/issues/291#issuecomment-283060736","issue_url":"https://api.github.com/repos/mozilla/telemetry-dashboard/issues/291","id":283060736,"user":{"login":"chutten","id":1123376,"avatar_url":"https://avatars.githubusercontent.com/u/1123376?v=3","gravatar_id":"","url":"https://api.github.com/users/chutten","html_url":"https://github.com/chutten","followers_url":"https://api.github.com/users/chutten/followers","following_url":"https://api.github.com/users/chutten/following{/other_user}","gists_url":"https://api.github.com/users/chutten/gists{/gist_id}","starred_url":"https://api.github.com/users/chutten/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chutten/subscriptions","organizations_url":"https://api.github.com/users/chutten/orgs","repos_url":"https://api.github.com/users/chutten/repos","events_url":"https://api.github.com/users/chutten/events{/privacy}","received_events_url":"https://api.github.com/users/chutten/received_events","type":"User","site_admin":false},"created_at":"2017-02-28T14:55:29Z","updated_at":"2017-02-28T14:55:29Z","body":"The dashboard as it stands is set to show rates instead of counts, so it'll require a little more effort to treat gpu crashes as a count. Shouldn't be too terrible.\r\n\r\nThat being said, I'm not sure that counts give us anything better than rates. So long as the proportion of the population getting gpu processes (and, thus, gpu crashes) is a representative %ge of the overall population, then it'll likely still follow the same weekly/seasonal ups and downs that the \"per-kilo-usage-hour\" rate was designed to normalize.\r\n\r\nI'll experiment a bit here and see what it looks like."}}
{"actor":{"display_login":"chutten"}}