Skip to content
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

[Impeller] Added tests to assert empty saveLayer behaviors. #47138

Merged
merged 1 commit into from
Oct 23, 2023

Conversation

gaaclarke
Copy link
Member

@gaaclarke gaaclarke commented Oct 19, 2023

fixes: flutter/flutter#126391

It turns out certain cases listed in the issue already render correctly. This adds tests to assert that we maintain that behavior.

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
  • I listed at least one issue that this PR fixes in the description above.
  • I added new tests to check the change I am making or feature I am adding, or the PR is test-exempt. See testing the engine for instructions on writing and running engine tests.
  • I updated/added relevant documentation (doc comments with ///).
  • I signed the CLA.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@gaaclarke gaaclarke requested a review from bdero October 19, 2023 23:57
Copy link
Member

@bdero bdero left a comment

Choose a reason for hiding this comment

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

LGTM!

@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 #47138 at sha 6de4b95

@chinmaygarde chinmaygarde changed the title [Impeller] added tests to assert empty saveLayer behaviors [Impeller] Added tests to assert empty saveLayer behaviors. Oct 21, 2023
@gaaclarke gaaclarke added the autosubmit Merge PR when tree becomes green via auto submit App label Oct 23, 2023
@gaaclarke gaaclarke merged commit abeab89 into flutter:main Oct 23, 2023
28 checks passed
fluttermirroringbot pushed a commit to flutter/flutter that referenced this pull request Oct 23, 2023
…137100)

flutter/engine@e89f042...abeab89

2023-10-23 30870216+gaaclarke@users.noreply.github.com [Impeller] Added tests to assert empty saveLayer behaviors. (flutter/engine#47138)
2023-10-23 skia-flutter-autoroll@skia.org Roll Skia from d534571c4bc3 to 73e9879f06e7 (1 revision) (flutter/engine#47233)
2023-10-23 chinmaygarde@google.com Add missing headers to the fml source_set. (flutter/engine#47232)
2023-10-23 jonahwilliams@google.com [Impeller] Vk query cleanups. (flutter/engine#47208)
2023-10-23 skia-flutter-autoroll@skia.org Roll Skia from 4976279e4441 to d534571c4bc3 (1 revision) (flutter/engine#47231)

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 jimgraham@google.com,rmistry@google.com,zra@google.com 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://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
harryterkelsen pushed a commit that referenced this pull request Oct 23, 2023
fixes: flutter/flutter#126391

It turns out certain cases listed in the issue already render correctly.
This adds tests to assert that we maintain that behavior.

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide] and the [C++,
Objective-C, Java style guides].
- [x] I listed at least one issue that this PR fixes in the description
above.
- [x] I added new tests to check the change I am making or feature I am
adding, or the PR is [test-exempt]. See [testing the engine] for
instructions on writing and running engine tests.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I signed the [CLA].
- [x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on [Discord].

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#overview
[Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene
[test-exempt]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[C++, Objective-C, Java style guides]:
https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
[testing the engine]:
https://github.com/flutter/flutter/wiki/Testing-the-engine
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes
[Discord]: https://github.com/flutter/flutter/wiki/Chat
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autosubmit Merge PR when tree becomes green via auto submit App e: impeller will affect goldens
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[Impeller] Empty subpasses should not be elided when they have "destructive" modifiers
2 participants