Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: a24ebae1381ed762e03757bad419403a1336d4fb
https://github.com/WebKit/WebKit/commit/a24ebae1381ed762e03757bad419403a1336d4fb
Author: Bryan Medina <[email protected]>
Date: 2025-10-15 (Wed, 15 Oct 2025)
Changed paths:
M Tools/Scripts/libraries/resultsdbpy/resultsdbpy/view/static/js/timeline.js
Log Message:
-----------
[ ResultsDB ] Modify 'Find Regression Point' button behavior on Results
Database
rdar://159977488
https://bugs.webkit.org/show_bug.cgi?id=298484
Reviewed by Jonathan Bedard.
The logic behind the 'Find Regression Point' button should be modified so it is
more accurate in finding real regressions. This can be done by comparing
success rate at a certain threshold of 10 UUIDs and then comparing before and
after a certain point, determining if it is a valid regression point or not.
* Tools/Scripts/libraries/resultsdbpy/resultsdbpy/view/static/js/timeline.js:
(commitsForResults): Added results in call for minimumUuidForResults
(TimelineFromEndpoint.prototype.reload): Finds regressions upon page load
(TimelineFromEndpoint.prototype.countSuccessfulTests): This is where successful
tests are tracked.
(TimelineFromEndpoint.prototype.detectRegression): This is where the threshold
is introduced that will validate a regression point.
(TimelineFromEndpoint.prototype.computedRegressionPoints): Regressions will be
computed here by comparing analysis windows.
(TimelineFromEndpoint.prototype.computeAndStoreRegressions): Once regressions
are caught, here is where the results are combined.
Canonical link: https://commits.webkit.org/301571@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-changes
