[results.webkit.org] Separate failures between runs sharing a configu…

…ration

https://bugs.webkit.org/show_bug.cgi?id=271807
rdar://125515440

Reviewed by Ryan Haddad.

* Tools/Scripts/libraries/resultsdbpy/resultsdbpy/view/static/js/investigate.js:
(_InvestigateDrawer.prototype.dispatch): Only assign a Failure object to a run if the UUID and
build time of the Failure match the current run.

Canonical link: https://commits.webkit.org/276786@main

Tools/Scripts/libraries/resultsdbpy/resultsdbpy/view/static/js/investigate.js

@@ -114,8 +114,6 @@ function prioritizedFailures(failures, max = 0, willFilterExpected = false)
         failuresToDisplay[max - 1] = null;
     }
 
-
-
     return `<div>${failuresToDisplay.map(failure => {
         if (failure === null) {
             const params = failures.toParams();
@@ -367,7 +365,11 @@ class _InvestigateDrawer {
             this.data.forEach(datum => {
                 datum.failures = new Failures(this.suite, datum.configuration);
                 failures.forEach(failure => {
-                    if (datum.configuration.compare(failure.configuration) === 0)
+                    if (
+                        datum.configuration.compare(failure.configuration) === 0 &&
+                        failure.uuid_range[0] <= datum.uuid && datum.uuid <= failure.uuid_range[1] &&
+                        failure.start_time_range[0] <= datum.start_time && datum.start_time <= failure.start_time_range[1]
+                    )
                         datum.failures = Failures.combine(datum.failures, failure);
                 });
             });