Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@bdero
Copy link
Member

@bdero bdero commented Jun 26, 2023

Part of flutter/flutter#128606.

  • Fix all of the Porter-Duff blends (virtually all of the blends were wrong). Still working on getting all of the advanced/color blends fixed up.
  • Fill in missing ops for arithmetic types/remove Vector4 conversions.
  • Remove the original GeometryTest in favor of the much clearer goldens. Once we have all of the CPU blends matching up properly with the GPU blends, we can think about constructing a more intentional test that covers a select number of important cases with accompanying explanation.

Top rectangles = GPU blends
Bottom rectangles = CPU blends

Before:

Screen.Recording.2023-06-22.at.4.45.25.PM.mov

After:

Screen.Recording.2023-06-26.at.1.55.55.PM.mov

@bdero bdero self-assigned this Jun 26, 2023
Copy link
Contributor

@jonahwilliams jonahwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

So we'll have goldens tracking these?

@flutter-dashboard
Copy link

Golden file changes have been found for this pull request. Click here to view and triage (e.g. because this is an intentional change).

If you are still iterating on this change and are not ready to resolve the images on the Flutter Gold dashboard, consider marking this PR as a draft pull request above. You will still be able to view image results on the dashboard, commenting will be silenced, and the check will not try to resolve itself until marked ready for review.

Changes reported for pull request #43217 at sha e1a67b1

@jonahwilliams
Copy link
Contributor

(Looks like yes, SGTM)

@bdero
Copy link
Member Author

bdero commented Jun 26, 2023

Yeah I got the CPU blends roped into the blend goldens as part of #43117.

@bdero bdero merged commit b310136 into flutter:main Jun 26, 2023
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Jun 27, 2023
auto-submit bot pushed a commit to flutter/flutter that referenced this pull request Jun 27, 2023
…129599)

flutter/engine@715eff2...f320b8c

2023-06-27 [email protected] [web] Removes patchCanvasKitModule. (flutter/engine#42941)
2023-06-26 [email protected] Roll ANGLE from cafbf6e2660f to cba77bceb26c (1 revision) (flutter/engine#43222)
2023-06-26 [email protected] [Impeller] Fix CPU Porter-Duff blends (flutter/engine#43217)
2023-06-26 [email protected] Roll Skia from c1effc01211e to 370132bcadb1 (2 revisions) (flutter/engine#43221)
2023-06-26 [email protected] Roll ANGLE from 4a4b13cc6931 to cafbf6e2660f (2 revisions) (flutter/engine#43219)
2023-06-26 [email protected] Roll Skia from 4ae209493390 to c1effc01211e (4 revisions) (flutter/engine#43218)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC [email protected],[email protected],[email protected] on the revert to ensure that a human
is aware of the problem.

To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
kjlubick pushed a commit to kjlubick/engine that referenced this pull request Jul 14, 2023
Part of flutter/flutter#128606.

* Fix all of the Porter-Duff blends (virtually all of the blends were
wrong). Still working on getting all of the advanced/color blends fixed
up.
* Fill in missing ops for arithmetic types/remove Vector4 conversions.
* Remove the original GeometryTest in favor of the much clearer goldens.
Once we have all of the CPU blends matching up properly with the GPU
blends, we can think about constructing a more intentional test that
covers a select number of important cases with accompanying explanation.

Top rectangles = GPU blends
Bottom rectangles = CPU blends
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

No open projects
Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants