- 10 Jun, 2019 1 commit
-
-
Todd Volkert authored
-
- 03 Jun, 2019 1 commit
-
-
- 01 Jun, 2019 1 commit
-
-
Chris Bracken authored
https://github.com/flutter/engine/compare/69ebe5fb28fc..68a3ca46b40a git log 69ebe5fb28fca271b23010d43d4dc7f6e5286c4f..a4b7d1c2895d82228705a021cdb7fdb2f71ac2a5 --no-merges --oneline 4c6253cdd Copy the macOS podspec during builds (#9158) 68a3ca46b Roll src/third_party/dart 445a23a9bc..0e6b74543c (29 commits) (#9159) 1d1cff1fa Roll src/third_party/skia 3cd435eecf5e..09f5aedf2cc8 (3 commits) (#9160) The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff (cbracken@google.com), and stop the roller if necessary.
-
- 25 Apr, 2019 1 commit
-
-
Jonah Williams authored
-
- 15 Apr, 2019 1 commit
-
-
Jonah Williams authored
-
- 21 Feb, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 19 Jan, 2019 1 commit
-
-
Ian Hickson authored
These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time.
-
- 21 Dec, 2018 2 commits
-
-
Ian Hickson authored
This reverts commit 76f70810.
-
Ian Hickson authored
* Remove many timeouts. These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time. * Get the attach tests to pass. * Apply review comments from Todd * More review comment fixes * Put back the extended timeouts here now that I know why we have them...
-
- 01 Oct, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 20 Sep, 2018 1 commit
-
-
Greg Spencer authored
This changes the compiler output for gradle to be less verbose and more easily read. This only applies to compilation error messages: other gradle messages will continue to print as before. It also fixes a small problem with the performance measurement printing (see that "7.1s" on it's own line in the original?) so that if something is expected to have multiple lines of output, it prints an initial line, and a "Done" line with the elapsed time, so that it's possible to know what the time applies to. It also updates the spinner to be fancier, at least on platforms other than Windows (which is missing a lot of symbols in its console font). Addresses #17307
-
- 14 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 12 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint unnecessary_new * fix tests * fix tests * fix tests
-
- 02 Aug, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 27 Jul, 2018 1 commit
-
-
Todd Volkert authored
It was causing problems rolling Flutter into Fuchsia
-
- 23 Jul, 2018 1 commit
-
-
Alexandre Ardhuin authored
* re-enable lint unnecessary_const * remove trailling whitespaces * remove unnecessary const (after merge)
-
- 20 Jul, 2018 1 commit
-
-
Leaf Petersen authored
* Remove uses of deprecated constants * Change int.parse to int.tryParse where appropriate
-
- 19 Jul, 2018 1 commit
-
-
Danny Tuppeny authored
* Make cleanup of flutter processes in tests more reliable * Fix quit signals I confused SigInt&SigTerm for SigTerm&SigKill when I first did this. SigTerm can be blocked and doesn't guarantee the process will be terminated. * Don't use deprecated constants * Fix typo * Add some additional info to debug buffer * Fix return types on Futures
-
- 16 Jul, 2018 2 commits
-
-
Ian Hickson authored
This reverts commit cc1cf13e.
-
Alexandre Ardhuin authored
-
- 13 Jun, 2018 1 commit
-
-
Chris Bracken authored
fuchsia_tester.dart still assumes Dart 1. Previously, it ran tests directly from source, flutter_platform.dart automatically runs a kernel compile when operating in Dart 2 mode, but this assumes a functional Dart SDK is available in the artifacts directly, and fuchsia_tester.dart mocks out the artifacts directory with an empty temp dir. Remaining work is: 1. Get the frontend server building as a dependency on Fuchsia. 2. Patch fuchsia_tester.dart to use a valid Dart SDK and frontend server. This also reverts migration to Dart 2 typedef syntax. This reverts commit 6c56bb24. (#18362) This reverts commit 3daebd05. (#18316)
-
- 11 Jun, 2018 1 commit
-
-
Greg Spencer authored
Now that Dart 1 is turned off, reapplying my change to turn on the prefer_generic_function_type_aliases analysis option, and fix all the typedefs to Dart 2 preferred syntax. Also eliminated the unused analysis_options_repo.yaml file and turned on public_member_api_docs in analysys_options.yaml. No logic changes, just changing the typedef syntax for all typedefs, and updating analysis options.
-
- 30 May, 2018 2 commits
-
-
Greg Spencer authored
Revert "Update typedef syntax to use Function notation and turn on lint for old notation. (#18035)" (#18041) This reverts commit 32586020.
-
Greg Spencer authored
Fixes #18028 Just changes typedef declarations, no logic changes.
-
- 04 May, 2018 2 commits
-
-
Todd Volkert authored
The new values are not ready for use yet inside Google
-
Yegor authored
* Roll engine to e976be13c51448f89107d082ec81e2b6731671fa * move away from deprecated constants
-
- 20 Apr, 2018 1 commit
-
-
Yegor authored
Fixes #13655
-
- 28 Mar, 2018 1 commit
-
-
Todd Volkert authored
This updates AppContext per the recommendations in #15352 Fixes #15352
-
- 14 Mar, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 26 Jan, 2018 1 commit
-
-
Ian Hickson authored
Also some trivial improvements to style.
-
- 06 Sep, 2017 1 commit
-
-
Mikkel Nygaard Ravn authored
-
- 04 May, 2017 1 commit
-
-
Todd Volkert authored
-
- 07 Apr, 2017 1 commit
-
-
Ian Hickson authored
Aggressively apply the const lint.
-
- 16 Mar, 2017 1 commit
-
-
Michael Goderbauer authored
It's no longer needed with the latest Dart SDK roll.
-
- 15 Mar, 2017 2 commits
-
-
Alexandre Ardhuin authored
-
Michael Goderbauer authored
* Make ProcessSignals portable This removes the need to wrap unsupported signals with in `if (!platform.isWindows) ..`. It also allows us to implement a work around for breaking the Windows console when flutter is exited with Ctrl+C. * review comments * adding tests * add license header
-
- 06 Mar, 2017 1 commit
-
-
Todd Volkert authored
-
- 01 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
-
- 26 Jan, 2017 1 commit
-
-
Todd Volkert authored
-
- 09 Jan, 2017 1 commit
-
-
Todd Volkert authored
This ensures that accidental usages of dart:io's file API don't creep in over time.
-