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

Deprecate --use-local-canvaskit flag #40680

Closed

Conversation

harryterkelsen
Copy link
Contributor

We should always use the locally-built CanvasKit in tests.

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 Hixie said 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.

@flutter-dashboard flutter-dashboard bot added the platform-web Code specifically for the web engine label Mar 27, 2023
@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@eyebrowsoffire
Copy link
Contributor

This is actually subsumed by my changes here: #39984

It's going to be a lot easier to wait for that, since that simultaneously switches us over to the engine_v2 recipes, so you don't have to worry about coordinating stuff with the old web_engine recipe (which uses this flag, hence why you are getting CI failures here).

@flutter-dashboard
Copy link

This pull request executed golden file tests, but it has not been updated in a while (20+ days). Test results from Gold expire after as many days, so this pull request will need to be updated with a fresh commit in order to get results from Gold.

@kevmoo
Copy link
Contributor

kevmoo commented Apr 18, 2023

Are we deprecating or removing? Tis different. 😄

@eyebrowsoffire
Copy link
Contributor

We're removing it. It's already gone with the web test reorganization, so we should just close this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs tests platform-web Code specifically for the web engine
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants