Rick Oosterholt
Rick Oosterholt
Thanks for the quick reply. WARN level would indeed help.
>Do you have an example project this can be with reproduced with? / can you provide one? I'm trying to create a demo situation for reproduction. I'll let you know....
Here are the test report files in the 'upstream job' (see [parallel-test-executor](https://plugins.jenkins.io/parallel-test-executor/)). [reports.zip](https://github.com/jenkinsci/junit-plugin/files/5542370/reports.zip)
@timja What is the best way of doing this. When I clone this repo I do not even see the 'src' directory for example.
Cool thanks. That's fast. Since I do not see the sources, how can I bisect?
Revision 3a90162733384353be4ca8ef138c3f7a63fecc51 is causing this issue.
@rpjesivac do you have the same job setup; are you also using the Parallel Test Executor plugin?
The 'Test-out.*' files are faulty. Files got duplicated while 'obfuscating' test reports. I've updated the reports.zip with the duplicated files removed. These are not the reason of the duplicated test...
Still no clue what is going on. I've added a archive artefacts post build step with the same `pattern` as the publish test result. The artefacts do not show any...
Additional information to clarify the situation. All tests are reported twice; see test result chart:  Also see any of the test suites; all test methods are reported twice: ...