1. 19 Apr, 2019 3 commits
  2. 15 Apr, 2019 1 commit
    • liyuqian's avatar
      Fix the warning test by checking stderr (#30997) · b0937a1e
      liyuqian authored
      Previously, I used the Android emulator for testing and everything
      seemed to work fine with stdout (if I remember correctly). But our
      devicelab uses real Android devices and the warnings are routed to
      stderr. Hence change stdout to stderr in the test.
      b0937a1e
  3. 10 Apr, 2019 1 commit
  4. 30 Mar, 2019 1 commit
  5. 29 Mar, 2019 1 commit
  6. 22 Mar, 2019 1 commit
  7. 10 Mar, 2019 1 commit
  8. 08 Mar, 2019 1 commit
  9. 01 Mar, 2019 1 commit
    • Alexandre Ardhuin's avatar
      Add missing trailing commas (#28673) · 387f8854
      Alexandre Ardhuin authored
      * add trailing commas on list/map/parameters
      
      * add trailing commas on Invocation with nb of arg>1
      
      * add commas for widget containing widgets
      
      * add trailing commas if instantiation contains trailing comma
      
      * revert bad change
      387f8854
  10. 27 Feb, 2019 1 commit
  11. 23 Feb, 2019 1 commit
  12. 22 Feb, 2019 1 commit
    • liyuqian's avatar
      Shader warm up (#27660) · a44f174e
      liyuqian authored
      This patch adds a default shader warm up process which moves shader compilation from the animation time to the startup time. This also provides an extension for `runApp` so developers can customize the warm up process.
      
      This should reduce our worst_frame_rasterizer_time_millis from ~100ms to ~20-30ms for both flutter_gallery and complex_layout benchmarks. Besides, this should also have a significant improvement on 90th and 99th percentile time (50%-100% speedup in some cases, but I haven't tested them thoroughly; I'll let our device lab collect the data afterwards).
      
      The tradeoff the is the startup time (time to first frame). Our `flutter run --profile --trace-startup` seems to be a little noisy and I see about 100ms-200ms increase in that measurement for complex_layout and flutter_gallery. Note that this only happens on the first run after install or data wipe. Later the Skia persistent cache will remove the overhead.
      
      This also adds a cubic_bezier benchmark to test the custom shader warm up process.
      
      This should fix https://github.com/flutter/flutter/issues/813 (either by `defaultShaderWarmUp`, or a `customShaderWarmUp`).
      a44f174e
  13. 15 Feb, 2019 1 commit
  14. 06 Feb, 2019 1 commit
    • Greg Spencer's avatar
      Make a kReleaseMode constant that is public. (#27502) · da27f623
      Greg Spencer authored
      Before this, we had several places where an isReleaseMode was defined, all with the same definition. This just makes it more broadly visible to allow our users to use it, as well as creating debug and profile versions, and adding a device lab test for it.
      
      Since this is a const value, this makes it possible for a developer to easily mark blocks that can be removed at AOT compile time.
      da27f623
  15. 05 Feb, 2019 1 commit
  16. 19 Jan, 2019 2 commits
  17. 14 Jan, 2019 1 commit
  18. 21 Dec, 2018 2 commits
    • Ian Hickson's avatar
      Revert "[O] Remove many timeouts. (#23531)" (#25646) · 8426910a
      Ian Hickson authored
      This reverts commit 76f70810.
      8426910a
    • Ian Hickson's avatar
      [O] Remove many timeouts. (#23531) · 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...
      76f70810
  19. 18 Dec, 2018 1 commit
  20. 14 Dec, 2018 1 commit
  21. 13 Dec, 2018 1 commit
  22. 12 Dec, 2018 1 commit
  23. 27 Nov, 2018 2 commits
  24. 16 Nov, 2018 1 commit
  25. 15 Nov, 2018 1 commit
  26. 10 Nov, 2018 1 commit
  27. 02 Nov, 2018 1 commit
  28. 30 Oct, 2018 1 commit
  29. 24 Oct, 2018 1 commit
  30. 23 Oct, 2018 2 commits
    • Michael Klimushyn's avatar
      Revert "E2E test setting and using isolate names (#23388)" (#23416) · e70f1952
      Michael Klimushyn authored
      This reverts commit 93573de2.
      
      Fails in the devicelab:
      
      ```
      run:stderr: A problem occurred evaluating project ':app'.
      run:stderr: > Could not resolve all files for configuration 'classpath'.2018-10-23T10:46:46.335864:
      run:stderr:    > Could not find aapt2-proto.jar (com.android.tools.build:aapt2-proto:0.3.1).2018-10-23T10:46:46.335960:
      run:stderr:      Searched in the following locations:2018-10-23T10:46:46.336048:
      ```
      e70f1952
    • Michael Klimushyn's avatar
      E2E test setting and using isolate names (#23388) · 93573de2
      Michael Klimushyn authored
      Adds an integration devicelab test that runs an Android app with two
      custom named isolates. Tests that the isolate names are present and that
      it's possible to attach to just one of the isolates.
      
      Fixes flutter/flutter#22009
      93573de2
  31. 22 Oct, 2018 1 commit
  32. 17 Oct, 2018 2 commits
  33. 10 Oct, 2018 1 commit
    • Greg Spencer's avatar
      Rename 'application' back to 'module', and make 'app' the default again for templates. (#22888) · 0ff9e8a9
      Greg Spencer authored
      We decided that redefining the default for templates was premature. We're going to go back to having "module" in experimental land again, and we'll try again when we have the feature set fully baked.
      
      This keeps the writing of the .metadata files, and writing the template type to them, because that was a good improvement, and there are still a bunch of added tests that improve our coverage.
      0ff9e8a9