it took some amount of time, to track down the problem - could just anyone take a look at this issue?

Change priority since an easy workaround exists, rename one of test adding a character like _

Are you running JUnit tests?

Thanx for responding

>Are you running JUnit tests?
yes, we are running junit-tests.

yes, renaming would be a workaround - but we have more than 1000 unit tests und unfortunately the hashcollsion is silent, so we dont know if it happens again (with other filenames)

i think a simple check, if the generated target file name exists (and then choosing a different name) would be fix.

File junitTargetFile = new File(parent, JUNIT_FILE_PREFIX + inputFile.hashCode() + JUNIT_FILE_POSTFIX);
while (junitTargetFile.exists()) {
    junitTargetFile = new File(parent, JUNIT_FILE_PREFIX + inputFile.hashCode()+"_"+ RandomStringUtils.randomAlphabetic(1) + JUNIT_FILE_POSTFIX);
}
...
//this method does not check, if the targetFile already exists.
inputMetric.convert(inputFile, junitTargetFile);

Ok, I was interested to make a proper unit test (also if hascode of file object depends from absolute path so depends from O.S. and your jenkins workspace path).

I'm already working on solution that is similar to yours but using UUID

Code changed in jenkins
User: Nikolas Falco
Path:
src/main/java/org/jenkinsci/plugins/xunit/XUnitDefaultValues.java
src/main/java/org/jenkinsci/plugins/xunit/service/XUnitConversionService.java
src/main/java/org/jenkinsci/plugins/xunit/service/XUnitTransformer.java
src/main/java/org/jenkinsci/plugins/xunit/types/CustomType.java
src/test/java/org/jenkinsci/plugins/xunit/service/XUnitConversionServiceTest.java
src/test/java/org/jenkinsci/plugins/xunit/service/XUnitTransformerTest.java
http://jenkins-ci.org/commit/xunit-plugin/2885f4f57ceaa1e816db07ca414285935b83c783
Log:
JENKINS-48945 Testreport lacks of those test in which the hashcode of two different testsuite name coincide

Use UUID instead the hashcode of the file to generate a unique converted test report.
By default java provides a version 4 UUID that ensure be unique in the same JVM instance. Since there are no more JVM that works with the same workspace is enough. A version 1 UUID that use MAC address to ensure file is unique over Jenkins nodes is not needed since XUnitProcessor does not copy slave node report files back to master.

Thank You  for solving this issue so fast

is there a plan, when this bugfix will be released? (its not part of Version: 1.103)