{"action":"opened","issue":{"url":"https://api.github.com/repos/technomancy/leiningen/issues/1859","labels_url":"https://api.github.com/repos/technomancy/leiningen/issues/1859/labels{/name}","comments_url":"https://api.github.com/repos/technomancy/leiningen/issues/1859/comments","events_url":"https://api.github.com/repos/technomancy/leiningen/issues/1859/events","html_url":"https://github.com/technomancy/leiningen/issues/1859","id":62520085,"number":1859,"title":"lein test eats top level exceptions","user":{"login":"SavageMessiah","id":376266,"avatar_url":"https://avatars.githubusercontent.com/u/376266?v=3","gravatar_id":"","url":"https://api.github.com/users/SavageMessiah","html_url":"https://github.com/SavageMessiah","followers_url":"https://api.github.com/users/SavageMessiah/followers","following_url":"https://api.github.com/users/SavageMessiah/following{/other_user}","gists_url":"https://api.github.com/users/SavageMessiah/gists{/gist_id}","starred_url":"https://api.github.com/users/SavageMessiah/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SavageMessiah/subscriptions","organizations_url":"https://api.github.com/users/SavageMessiah/orgs","repos_url":"https://api.github.com/users/SavageMessiah/repos","events_url":"https://api.github.com/users/SavageMessiah/events{/privacy}","received_events_url":"https://api.github.com/users/SavageMessiah/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-17T21:14:33Z","updated_at":"2015-03-17T21:14:33Z","closed_at":null,"body":"If a clojure.lang.ExceptionInfo makes it to the top level of lein test it just outputs \"Tests failed.\" instead of printing a stacktrace or anything useful.\r\n\r\nI'm currently running into an issue where lein test terminates with that message (and nothing else) consistently and I have no way to determine the reason for the failure except by deploying a custom build of leiningen to our CI server."}}