Skip to content

Conversation

@gaaclarke
Copy link
Member

@gaaclarke gaaclarke commented Sep 2, 2022

Adds integration tests for isolate platform channels on macos.

engine pr: flutter/engine#35893

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, including Features we expect every widget to implement.
  • I signed the CLA.
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • 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 framework flutter/packages/flutter repository. See also f: labels. c: contributor-productivity Team-specific productivity, code health, technical debt. labels Sep 2, 2022
@gaaclarke gaaclarke force-pushed the isolate-platform-channels-macos branch 3 times, most recently from 4b5c7b7 to d060784 Compare September 15, 2022 20:42
@gaaclarke gaaclarke changed the title Isolate platform channels for macos Isolate platform channels for desktop Sep 15, 2022
@gaaclarke gaaclarke marked this pull request as ready for review September 15, 2022 20:43
@gaaclarke gaaclarke requested a review from dnfield September 15, 2022 20:43
@gaaclarke gaaclarke force-pushed the isolate-platform-channels-macos branch from d060784 to 28edad9 Compare September 15, 2022 20:44
@gaaclarke gaaclarke changed the title Isolate platform channels for desktop Isolate platform channels for macos Sep 15, 2022
@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.

@goderbauer goderbauer requested a review from a-wallen September 20, 2022 22:10
@a-wallen
Copy link
Contributor

(triage) looks like this one is still active and waiting for an engine PR to land.

@gaaclarke
Copy link
Member Author

This is ready to review @a-wallen and @dnfield. We just can't land it until the engine PR is merged. The integration test isn't run as part of the presubmit tests.

@gaaclarke
Copy link
Member Author

The engine pr rolled in #112025

@gaaclarke gaaclarke merged commit 5a7b0bd into flutter:master Sep 21, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/plugins that referenced this pull request Sep 22, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/plugins that referenced this pull request Sep 22, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Sep 22, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/plugins that referenced this pull request Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt. framework flutter/packages/flutter repository. See also f: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants