Tim Jacomb

There's a PR for it here that needs some minor fixing up: https://github.com/jenkinsci/junit-plugin/pull/98

There’s no guarantee the test file will have been changed in the PR though right? Is there a value in annotating one that hasn’t changed?

that doesn't look like the right stacktrace, is there another one before or after? also any chance you update the build names and they are duplicates?

could be https://issues.jenkins.io/browse/JENKINS-63338

Thanks! That’s useful will try get back to this at some point

Needs a unit test, some more expansion on the use case would be useful

not without the review comment being addressed

> Those who don't care about the Git history at all and are OK with a "Git wall", including re-indenting pom.xml files and e.g. reformatting all Java files with Google...

If I knew how to reproduce it I could fix it, but I just can't seem to reproduce this on demand. (We have this happening in our production instance too)...

Looks to be caused by https://github.com/jenkinsci/junit-plugin/pull/199/files#diff-4fa8f2162a640cc3f024dadbffc9b442ab73e2afd30e5030ec0088ac300371e5L78 This should go away if you reconfigure your job