Clean up groovy stack traces #758
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Groovy stacktraces are basically unreadable, so any that are thrown we clean up using the groovy-provided StackTraceUtils class.
|
Note that this did pass two of the builds in the matrix. The android one, which seems a bit flaky, timed out. |
|
@tomdcc Yes, there have been and still are problems with the Travis builds, see this mailing thread |
aslakhellesoy
added a commit
that referenced
this pull request
Aug 29, 2014
Clean up groovy stack traces
|
Thanks @tomdcc ! |
|
Awesome, thanks! |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Groovy stacktraces are basically unreadable, so any that are thrown we
clean up using the groovy-provided StackTraceUtils class.