{"action":"created","issue":{"url":"https://api.github.com/repos/ldionne/metabench/issues/145","repository_url":"https://api.github.com/repos/ldionne/metabench","labels_url":"https://api.github.com/repos/ldionne/metabench/issues/145/labels{/name}","comments_url":"https://api.github.com/repos/ldionne/metabench/issues/145/comments","events_url":"https://api.github.com/repos/ldionne/metabench/issues/145/events","html_url":"https://github.com/ldionne/metabench/issues/145","id":172504668,"number":145,"title":"Travis time limit blown up","user":{"login":"brunocodutra","id":4043663,"avatar_url":"https://avatars.githubusercontent.com/u/4043663?v=3","gravatar_id":"","url":"https://api.github.com/users/brunocodutra","html_url":"https://github.com/brunocodutra","followers_url":"https://api.github.com/users/brunocodutra/followers","following_url":"https://api.github.com/users/brunocodutra/following{/other_user}","gists_url":"https://api.github.com/users/brunocodutra/gists{/gist_id}","starred_url":"https://api.github.com/users/brunocodutra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brunocodutra/subscriptions","organizations_url":"https://api.github.com/users/brunocodutra/orgs","repos_url":"https://api.github.com/users/brunocodutra/repos","events_url":"https://api.github.com/users/brunocodutra/events{/privacy}","received_events_url":"https://api.github.com/users/brunocodutra/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-08-22T17:08:01Z","updated_at":"2016-08-23T02:47:32Z","closed_at":null,"body":"After the recent inclusion of new algorithms some builds have been [blowing up Travis time limit](https://travis-ci.org/ldionne/metabench/jobs/154068674).\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/ldionne/metabench/issues/comments/241611888","html_url":"https://github.com/ldionne/metabench/issues/145#issuecomment-241611888","issue_url":"https://api.github.com/repos/ldionne/metabench/issues/145","id":241611888,"user":{"login":"brunocodutra","id":4043663,"avatar_url":"https://avatars.githubusercontent.com/u/4043663?v=3","gravatar_id":"","url":"https://api.github.com/users/brunocodutra","html_url":"https://github.com/brunocodutra","followers_url":"https://api.github.com/users/brunocodutra/followers","following_url":"https://api.github.com/users/brunocodutra/following{/other_user}","gists_url":"https://api.github.com/users/brunocodutra/gists{/gist_id}","starred_url":"https://api.github.com/users/brunocodutra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brunocodutra/subscriptions","organizations_url":"https://api.github.com/users/brunocodutra/orgs","repos_url":"https://api.github.com/users/brunocodutra/repos","events_url":"https://api.github.com/users/brunocodutra/events{/privacy}","received_events_url":"https://api.github.com/users/brunocodutra/received_events","type":"User","site_admin":false},"created_at":"2016-08-23T02:47:32Z","updated_at":"2016-08-23T02:47:32Z","body":"> Changing `MEDIAN_OF` to `1` seems like a bad idea, since we implemented this precisely to make the timings more accurate\r\n\r\nWhile I agree with this in theory, the prevalence of negative timings in practice make me wonder whether `MEDIAN_OF 3` is indeed improving things that much to justify builds taking three times longer to run.\r\n\r\n>  I guess what we could do is reduce the size of lists to at most 100 on GCC only?\r\n\r\nTBH I'd rather lower the limit for every compiler equaly, because the way the benchmark module is setup today doesn't make it feasible to have ranges depend on compilers without a major refactoring. Plus we will probably start having problems with other compilers once we add missing benchmark cases anyways.\r\n\r\n"}}
{"actor":{"display_login":"brunocodutra"}}