{"action":"created","issue":{"url":"https://api.github.com/repos/scala/scala-jenkins-infra/issues/169","repository_url":"https://api.github.com/repos/scala/scala-jenkins-infra","labels_url":"https://api.github.com/repos/scala/scala-jenkins-infra/issues/169/labels{/name}","comments_url":"https://api.github.com/repos/scala/scala-jenkins-infra/issues/169/comments","events_url":"https://api.github.com/repos/scala/scala-jenkins-infra/issues/169/events","html_url":"https://github.com/scala/scala-jenkins-infra/issues/169","id":144691829,"number":169,"title":"test suite: keep going on failure, run --update-check and push results to github","user":{"login":"adriaanm","id":91083,"avatar_url":"https://avatars.githubusercontent.com/u/91083?v=3","gravatar_id":"","url":"https://api.github.com/users/adriaanm","html_url":"https://github.com/adriaanm","followers_url":"https://api.github.com/users/adriaanm/followers","following_url":"https://api.github.com/users/adriaanm/following{/other_user}","gists_url":"https://api.github.com/users/adriaanm/gists{/gist_id}","starred_url":"https://api.github.com/users/adriaanm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adriaanm/subscriptions","organizations_url":"https://api.github.com/users/adriaanm/orgs","repos_url":"https://api.github.com/users/adriaanm/repos","events_url":"https://api.github.com/users/adriaanm/events{/privacy}","received_events_url":"https://api.github.com/users/adriaanm/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/scala/scala-jenkins-infra/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-03-30T19:09:36Z","updated_at":"2016-04-04T20:07:35Z","closed_at":null,"body":"if the junit test suite fails, we won't see output from partest\r\n\r\nif partest fails, it would be great to re-run it with --update-check --failed and push the changes to some repo so we can analyze them outside of jenkins\r\n\r\nanything we can do to make it super easy to take a jenkins job and pick up where it failed on our local machines is worth doing"},"comment":{"url":"https://api.github.com/repos/scala/scala-jenkins-infra/issues/comments/205472729","html_url":"https://github.com/scala/scala-jenkins-infra/issues/169#issuecomment-205472729","issue_url":"https://api.github.com/repos/scala/scala-jenkins-infra/issues/169","id":205472729,"user":{"login":"som-snytt","id":369425,"avatar_url":"https://avatars.githubusercontent.com/u/369425?v=3","gravatar_id":"","url":"https://api.github.com/users/som-snytt","html_url":"https://github.com/som-snytt","followers_url":"https://api.github.com/users/som-snytt/followers","following_url":"https://api.github.com/users/som-snytt/following{/other_user}","gists_url":"https://api.github.com/users/som-snytt/gists{/gist_id}","starred_url":"https://api.github.com/users/som-snytt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/som-snytt/subscriptions","organizations_url":"https://api.github.com/users/som-snytt/orgs","repos_url":"https://api.github.com/users/som-snytt/repos","events_url":"https://api.github.com/users/som-snytt/events{/privacy}","received_events_url":"https://api.github.com/users/som-snytt/received_events","type":"User","site_admin":false},"created_at":"2016-04-04T20:07:35Z","updated_at":"2016-04-04T20:07:35Z","body":"I'm not up to speed on the issue, but having a single test framework (such as under junit) is a great goal, even if functions like update-check have to be pushed out to a tool.\r\n\r\nThe possible differentiator may be, \"fast\" tests are junit, while \"slow\" tests are partest, where a slow test requires initing a compiler."}}