-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Re-land Local & Pre-Submit Support for Skia Gold #43371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
It looks like this pull request includes a golden file change. Please make sure to follow Handling Breaking Changes. While there are exceptions to this rule, if this patch modifies an existing golden file, it is probably not an exception. Only new golden files are not considered breaking changes. Writing a golden file test for Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
|
|
||
| if (result.passed) { | ||
| return true; | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prior version called isValidDigestForExpectation here, to collect potential valid failures as the comparator searched for a positive.
In this case, it may needlessly make this call multiple times before finding a positive.
| failureDiffs[expectation] = result; | ||
| } | ||
| failureDiffs.forEach((String expectation, ComparisonResult result) async { | ||
| if (await skiaClient.isValidDigestForExpectation(expectation, golden.path)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting to make this call until there is no positive found will save a lot of calls, as it will only reach this point when a change has been detected.
|
cc/ @kjlubick I changed the use case of the |
goderbauer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
I hope to have the QPS limit on details/ live by EOD today. Will ping the bug when they are live. |
|
Change to gold is live to take more traffic on /json/details |
|
Performed an all-fail load test this morning and experienced no issues. 🎉 I also found that our post-submit LUCI builds were falling back to the Local comparator, so I'm re-applying the Skip comparator for those environments. The Post-submit comparator is used on Cirrus, so having the Local comparator running on LUCI, making additional requests, is unnecessary. |
Description
This will re-land the changes introduced in #40710, which were reverted after golden file tests started to time out when making requests to the
details/api.What's Changed
Noted below, the case for querying the
details/api has been changed.Before:
details/were checked for each failure while looking for a positiveNow:
details/are only checked after no positive has been found, rather than in step with the initial pass throughThe
details/api is also scheduled for performance improvements, tracking available here https://bugs.chromium.org/p/skia/issues/detail?id=9557 for Gold side changes.Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?