{"action":"opened","issue":{"url":"https://api.github.com/repos/catapult-project/catapult/issues/3050","repository_url":"https://api.github.com/repos/catapult-project/catapult","labels_url":"https://api.github.com/repos/catapult-project/catapult/issues/3050/labels{/name}","comments_url":"https://api.github.com/repos/catapult-project/catapult/issues/3050/comments","events_url":"https://api.github.com/repos/catapult-project/catapult/issues/3050/events","html_url":"https://github.com/catapult-project/catapult/issues/3050","id":192582758,"number":3050,"title":"Results on the perf dashboard are out of order","user":{"login":"primiano","id":7137473,"avatar_url":"https://avatars.githubusercontent.com/u/7137473?v=3","gravatar_id":"","url":"https://api.github.com/users/primiano","html_url":"https://github.com/primiano","followers_url":"https://api.github.com/users/primiano/followers","following_url":"https://api.github.com/users/primiano/following{/other_user}","gists_url":"https://api.github.com/users/primiano/gists{/gist_id}","starred_url":"https://api.github.com/users/primiano/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/primiano/subscriptions","organizations_url":"https://api.github.com/users/primiano/orgs","repos_url":"https://api.github.com/users/primiano/repos","events_url":"https://api.github.com/users/primiano/events{/privacy}","received_events_url":"https://api.github.com/users/primiano/received_events","type":"User","site_admin":false},"labels":[{"id":242943695,"url":"https://api.github.com/repos/catapult-project/catapult/labels/Bug","name":"Bug","color":"fc2929","default":false},{"id":250159481,"url":"https://api.github.com/repos/catapult-project/catapult/labels/Perf%20Dashboard","name":"Perf Dashboard","color":"207de5","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-30T14:42:13Z","updated_at":"2016-11-30T14:42:13Z","closed_at":null,"body":"I was investigating this weird bimodality with @perezju  and @chromy \r\n\r\n![screen shot 2016-11-30 at 2 35 10 pm](https://cloud.githubusercontent.com/assets/7137473/20756432/92868206-b70a-11e6-9270-d3ab1776c544.png)\r\n\r\nhttps://chromeperf.appspot.com/report?sid=759814305e5ead01db7fe16e5a2adbe189b1643bc0a0790dc9a2af0830cc8f54&start_rev=431846&end_rev=433499\r\n\r\nTurns out this is not bimodality. The points on the waterfall are not in order in that range.\r\nIf you hover on consecutive points you can see that the datetimes are not monotonic, nor are the build IDs. They are for the steady states on the far left and right, where the graph is stable.\r\n\r\nIn other words, for for consecutive runs in the window that goes up and down, I got this:\r\n```\r\nPoint ID   Datetime                   Position Range   Bot build id\r\n432219     2016-11-17T11:53:08.000Z   432196 - 432219  3794    \r\n432222     2016-11-16T10:12:55.000Z   432220 - 432222  3784    \r\n432262     2016-11-16T13:13:21.000Z   432223 - 432262  3785    \r\n432274     2016-11-17T14:42:24.000Z   432263 - 432274  3795    \r\n```\r\n\r\nnote how datetimes and bot build ids are out of order.\r\nAt this point I suspect the position range is just wrong.\r\n\r\nIn other words I think that what's happening here is that there is a standard regressions, but the data on the waterfall is out of order and we mix points before and after."}}
{"actor":{"display_login":"primiano"}}