Skip to content

Conversation

@ditman
Copy link
Member

@ditman ditman commented May 3, 2022

There have been a few changes in the hit order + semantics implementations on the Flutter Web engine. Some tests were added, but those can only run on master, with the new semantics approach.

This change skips those tests unless the "new semantics" are available (runs in master but skips in stable).

Unblocks: #1726

No CHANGELOG change: this code should be reverted in a few days.

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 relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
  • I signed the CLA.
  • The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
  • I listed at least one issue that this PR fixes in the description above.
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
  • I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
  • 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.

Copy link
Collaborator

@stuartmorgan-g stuartmorgan-g left a comment

Choose a reason for hiding this comment

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

LGTM with one question about how we skip.

Feel free to either land, or push this to my PR, as you prefer.


if (!_newSemanticsAvailable()) {
print('Skipping test: Needs flutter > 2.10');
return;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could we do these via skip, or do you actually have to run main and pumpAndSettle to be able to do the check?

Not a big deal either way since it's temporary code.

Copy link
Member Author

@ditman ditman May 3, 2022

Choose a reason for hiding this comment

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

Yeah, I tried to find a way to do a proper skip, but I couldn't call skip, because the check that I do is at runtime (it needs to look at the html code of a rendered app). If we could do: skip: !isMaster, I'd prefer to do that :P (but yeah, this is very temporary)

@ditman
Copy link
Member Author

ditman commented May 3, 2022

I'm going to cherry-pick this into @stuartmorgan's PR, so we can land both the fix+enabling of tests at the same time.

@ditman ditman closed this May 3, 2022
@ditman
Copy link
Member Author

ditman commented May 3, 2022

Changes cherry-picked into #1726

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants