jenkins cannot tell different tests apart if they are excersing the same test but with different settings

[tchaikov]

we run the same test with debug build and release build for multiple times. sometimes, only a single run fails. but all runs testing the same test case share the same identifier in JUnit test result XML files. so, despite that we are aware that the test foo-bar-baz with debug build fails, if we follow the link to the failing test, jenkins may or may not bring us to the failed test. we have to refresh multiple time to get the failure. for instance, in https://jenkins.scylladb.com/job/scylla-master/job/scylla-ci/4533/, the test of test_tablets.test_topology_changes failed. but the link of https://jenkins.scylladb.com/job/scylla-master/job/scylla-ci/4533/testReport/junit/(root)/test_tablets/Tests___Unit_Tests___test_topology_changes/ actually can point to one of the tests. it's schrodinger's test result!

this problem also manifested when we have test failures in the boost tests, and it was fixed by 421331a . unfortunately, we don't have the fix for the non-boost tests yet.

[tchaikov]

@benipeled hi Beni, JFYI, i just created this issue. so we can track it better.

[nyh]

Seen again in https://jenkins.scylladb.com/job/scylla-master/job/scylla-ci/9082/testReport/junit/(root)/test_topology_recovery_basic/test_topology_recovery_basic_6/
@kbr-scylla sent this link as an example of failure, but when I went to this link, I saw success.
@kbr-scylla said: "what jenkins shows is non-deterministic. Try to close the page and open it again. In some cases you should see a failed test report, and in some cases, a "passed test"..."