{"action":"opened","issue":{"url":"https://api.github.com/repos/travis-ci/travis-ci/issues/9666","repository_url":"https://api.github.com/repos/travis-ci/travis-ci","labels_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/9666/labels{/name}","comments_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/9666/comments","events_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/9666/events","html_url":"https://github.com/travis-ci/travis-ci/issues/9666","id":326716111,"number":9666,"title":"Adding a no timeout limit to travis.yml","user":{"login":"jakirkham","id":3019665,"avatar_url":"https://avatars1.githubusercontent.com/u/3019665?v=4","gravatar_id":"","url":"https://api.github.com/users/jakirkham","html_url":"https://github.com/jakirkham","followers_url":"https://api.github.com/users/jakirkham/followers","following_url":"https://api.github.com/users/jakirkham/following{/other_user}","gists_url":"https://api.github.com/users/jakirkham/gists{/gist_id}","starred_url":"https://api.github.com/users/jakirkham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jakirkham/subscriptions","organizations_url":"https://api.github.com/users/jakirkham/orgs","repos_url":"https://api.github.com/users/jakirkham/repos","events_url":"https://api.github.com/users/jakirkham/events{/privacy}","received_events_url":"https://api.github.com/users/jakirkham/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-26T06:57:13Z","updated_at":"2018-05-26T06:57:13Z","closed_at":null,"author_association":"NONE","body":"Would be nice to have a configurable parameter in `travis.yml` to simply override the timeout limit for jobs being too quiet. For example, CircleCI provides the [`no_output_timeout` parameter]( https://circleci.com/docs/2.0/configuration-reference/#run ), which allows the user to override this limit if they know their build will be quiet for a bit.\r\n\r\nShould add this often becomes a necessity as one may bounce back and forth between going over the log length/size limit or being too quiet. Both situations lead to the job being terminated. It would be nice to soften one of these bounds when they become unreasonably tight for a particular job.\r\n\r\nAdmittedly there is the `travis_wait` script. However this isn't always honored and sometimes has other problems. Instead of spending time working on this script, it would be nice to just provide users' this simple configuration parameter to achieve the intended result without side effects."}}
{"actor":{"display_login":"jakirkham"}}