Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 1c7ffdc4d2928bf5bef66b0744c88bb7b89587c8
https://github.com/WebKit/WebKit/commit/1c7ffdc4d2928bf5bef66b0744c88bb7b89587c8
Author: Claudio Saavedra <[email protected]>
Date: 2026-09-03 (Thu, 03 Sep 2026)
Changed paths:
M
Tools/Scripts/libraries/resultsdbpy/resultsdbpy/view/static/js/investigate.js
Log Message:
-----------
[resultsdbpy] Fix investigate drawer not loading failures for WPE runs that
share a revision with the legacy API
https://bugs.webkit.org/show_bug.cgi?id=319694
Reviewed by Jonathan Bedard.
Configuration.compare() treats an unset member as matching any value, so two
configurations that differ only by an optional member compare as equal. For
example WPE reports both the default and the wpe-legacy-api flavor for the same
revision, and clicking either run aggregates both into the drawer.
The drawer then fetched the failures with the aggregate configuration and a
single start time. That pinned the flavor to one of the runs while pinning the
time to the other, so the query matched nothing and no failures were shown.
Query with the members that differ between the aggregated runs left unset, and
with a time range spanning all of them, so every run is returned and sorted
into its own report.
Canonical link: https://commits.webkit.org/320407@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
