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"?
Hello Oleksandr,
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
Thanks,
Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.