For my Gradle based pipeline I see stripped stack traces for failed test without any console logging context.
Java stack traces contains the most important info at the bottom and this part is stripped ((
It takes 3 min to collect/parse *test/*.xml report files while total build/test execution time of Gradle itself is 5 min.
So test report scan feature is useless and time consuming.
How can I disable this "feature"?
Currently you cannot disable the test reporting feature. The closest workaround would be to remove the files before the build finishes, which will make the parser not find any files to parse.
Can you open a feature request with some more details about the size of your stack trave here: https://bitbucket.org/site/master/issues/new
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events