Description of problem:

During 1.18 vs 1.19 regression testing, we observed a difference in PR/TR count present in the cluster, with the details recorded in the ResultsDB.

Close to ~170 entries were missing for PR and ~30 entries for TRs in the Tekton Results DB in the latest release of 1.19 version. The data for ResultsDB was captured at the end of the test when gathering the results (which should be over 1hour duration since the last PR creation, ideally giving enough time to sync all PR/TR information).

Prowjob:

• 1.18: 

  1950183308935565312

  1950110669051269120

• 1.19:

  1950183309011062784

  1950110670733185024

**

Test Artifacts:

• https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_release/67205/rehearse-67205-pull-ci-openshift-pipelines-performance-main-tkn-res-downstream-1-19-s3-locust-2-lsr/1950183309011062784/artifacts/tkn-res-downstream-1-19-s3-locust-2-lsr/openshift-pipelines-scaling-pipelines/artifacts/

Report:https://docs.google.com/document/d/156iBOAZA6DRd7m8C1WMHSeHL83HhIqG1V1_8HHtTliU/edit?tab=t.jer8o55ogwr

*Datasheet Points: https://docs.google.com/spreadsheets/d/1y8FQql5mMBH5VPgnNgd6vnpYQuwgCiCU0FNbgboDgO8/edit?gid=1257478274#gid=1257478274*

Prerequisites (if any, like setup, operators/versions):

Pipelines v1.19 and  v1.18

Steps to Reproduce

Trigger jobs in CI release with prow commands as shown here:

• https://github.com/openshift/release/pull/67205

/pj-rehearse pull-ci-openshift-pipelines-performance-main-tkn-res-downstream-1-18-s3-locust-2-lsr pull-ci-openshift-pipelines-performance-main-tkn-res-downstream-1-19-s3-locust-2-lsr