See failures in, for example,

https://jenkins.onap.org/job/dcaegen2-services-pm-mapper-review-verification-maven-master/10/

https://jenkins.onap.org/job/dcaegen2-services-pm-mapper-merge-verification-maven-master/4/

10 out of 15 pmmapper suite test cases failed due to missing docker logs on May 26 between successful executions of the same jobs before and after (without any changes done to either repository itself or any dependencies that should have had this effect on the results):

https://jenkins.onap.org/job/dcaegen2-services-pm-mapper-review-verification-maven-master/5/

https://jenkins.onap.org/job/dcaegen2-services-pm-mapper-merge-verification-maven-master/1/

https://jenkins.onap.org/job/dcaegen2-services-pm-mapper-review-verification-maven-master/12/

https://jenkins.onap.org/job/dcaegen2-services-pm-mapper-merge-verification-maven-master/5/

The entire LF Infra was apparently having issues at this time as, for example, Jira was almost unaccessible for a while (and at the same time the same test cases were passing perfectly well when executed on clean local development environment), so this suggests that the test cases were suffering from some sort of timing issues caused by unusual load.

There is also another issue that didn't seem to be caused by the load but some other random factor - this can be seen under

https://jenkins.onap.org/job/dcaegen2-services-pm-mapper-review-verification-maven-master/8/

...where one of the filesprocessingconfigpmmapper tests randomly failed to

Pm-mapper drop: 0 messages. Expected drop count: 6-9

(I have seen this happen once also in local tests)

This may warrant a separate Jira on further inspection, but I*m just mentioning it here for now