Closed itamararjuan closed 1 year ago
Thanks for taking the time to propose a fix. I recently released v2.0.0, please give that a try and see if it fixes the bug you encountered. If not, feel free to open a new issue. I no longer intend to maintain the v1 branch, so I'm closing this PR.
We use the
go-junit-report
in our Go project so that CircleCI will be able to read and summarize our test results clearerHowever, since our system logging is verbose and can generate tremendous amounts of logs this is something that we struggle with and were hoping can be addressed and this PR composes our our solution to this bug which is a hugh time saver for us in terms of realizing what has gone wrong with a given test
In addition, (specifically to our case anyway) this helps us reduce the total build time since our log artifacts are much smaller now since they don't need to contain massive amount of unused logs