[flutter_migrate] Skip slow tests #3270
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently
flutter_migrate
unit tests take 10 minutes to run, which is 1/6 of our total time allowance for a Cirrus test run, and 1-2 orders of magnitude slower than all of our other unit tests.This skips the slow tests, with references to a tracking issue. At some point when there are more eng resources on
flutter_migrate
someone can revisit these tests to speed them up and/or make them another type of test (such as a customrun_tests
test).Part of flutter/flutter#121257
Pre-launch Checklist
dart format
.)[shared_preferences]
pubspec.yaml
with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.CHANGELOG.md
to add a description of the change, following repository CHANGELOG style.///
).