[
https://issues.apache.org/jira/browse/PHOENIX-5814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073898#comment-17073898
]
Istvan Toth commented on PHOENIX-5814:
--------------------------------------
Some more explanation why I think that this is a good idea:
Our test suites are in a bad shape, but we often don't get enough information
from the trimmed stack traces about the problem.
This should make the test failures (especially the flaky hairy ones) more
actionable.
If someone is in the process of developing tests, and the output is too much,
it's really easy to turn trimming back on.
I have added the PR for all five repos.
Each one simply adds <trimStackTrace>false</trimStackTrace> to the
pluginManagement section of the parent pom,
except for phoenix, where I also did some consolidation of the common
configuration parameters.
It would be nice to get a general +1 to all five repos, so that this does not
drag forever.
(Provided that enough ppl agree that this is a good idea)
Just getting this into the main phoenix repo would be a win.
Alternatively, we could add the same to the Jenkins jobs, but that would be my
second choice.
> disable trimStackTrace
> ----------------------
>
> Key: PHOENIX-5814
> URL: https://issues.apache.org/jira/browse/PHOENIX-5814
> Project: Phoenix
> Issue Type: Improvement
> Components: connectors, core, omid, queryserver, tephra
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The default trimStackTrace=true maven setting is quite effective at making
> test output useless for all but the trivial failures.
> I propose setting it to false everywhere (i.e all five repos)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
