* iupdate engine version to 141176b9004d7b01325629fd45b2ef61b0d00251
* update engine version to f192c59d76c0afe63f2290c3ed76061f00c77cc7
This rolls dart to version 0175f24b2549732d0010708988fd328440c3f956
* Move dart 2 tests back to optional section to allow debugging of a new
regression in the petitParser package.
* Update
* Run flutter tests in preview-dart-2 mode on travis flutter builds.
* Run dart2 tests on osx. Run dart tests in dart2.
* Fix name camelCase
* Default options to empty array, rather than null
* Troubleshoot failures
* More logging
* Troubleshoot: run single test
* Troubleshoot: run 15 tests
* Troubleshoot: run 15 tests with fix
* Try limit concurrency to 1
* Limit concurrency for preview-dart-2 tests to 4
* Move dart2 tests to allow_failures section
* Reinstate tests_dart_2 shard
* Raise concurrency to 8
* Reuse compiler across multiple test runs
* Allow to switch entry points when recompiling.
Actually use single compiler to incrementally recompile all tests executed by 'flutter test'.
* Remove leftover commented code
* Fix comment
* Lints
* iOS works
* Works on Android
* Take in commit number in iOS also. Get rid of image upload for Android. It's just a waste of bandwidth
* Tweak to fix on Travis
Generate the "version" file from git tags.
Remove the old VERSION file and mentions of versions in pubspec.yaml files.
Replace the old update_versions.dart script with a new roll_dev.dart script.
Update "flutter channel".
Update "flutter upgrade", including making it transition from alpha to dev.
Update "flutter --version" and "flutter doctor".
In a Travis environment, the test package is exiting the process after
completing the tests.
See dart-lang/test@d1057c4
The flutter test command calls the test package's main() and then expects to
do other work afterward. The exit prevents flutter test from writing the
new coverage results, causing the coveralls tool to run against an old
lcov.info file.
This time, do so in Travis' sudo-enabled environment,
which is said to be less prone to networking issues.
It also means we'll run in an env with 7.5GB of RAM
instead of 4GB or RAM (at the cost of about 45 seconds
of extra boot-up time).
https://github.com/flutter/flutter/issues/10940
* configs for firebase hosting
* use the implicit FIREBASE_TOKEN
* don't print every command (lowers the chance of printing secret env vars, and for realz only deploy when merging into master
This moves all the bot-related files to `dev/bots`, hiding it from our
home page in github. Also, simplifies the travis setup, though that
doesn't do any difference to the performance sadly.
Turns out that ignoring all error lines that match the empty string is a
poor way to go.
Also, we have to update all the example packages now too, since we
analyze them. So just have travis use our update script.
Also, remove flutter_tools' old travis stuff. It's now part of a bigger
repo.
Also, make travis use the dev Dart SDK, since we need the new analyzer.
Stable is way too out of date, e.g. it still complains about libraries
not having names and mixins using 'super', and the strong mode hints are
even more aggressive than on dev.