1. 04 Mar, 2017 1 commit
  2. 03 Mar, 2017 1 commit
  3. 21 Feb, 2017 1 commit
  4. 20 Feb, 2017 1 commit
  5. 17 Feb, 2017 2 commits
  6. 16 Feb, 2017 1 commit
  7. 14 Feb, 2017 1 commit
  8. 28 Jan, 2017 1 commit
  9. 26 Jan, 2017 1 commit
  10. 24 Jan, 2017 1 commit
  11. 23 Jan, 2017 1 commit
  12. 19 Jan, 2017 1 commit
    • Ian Hickson's avatar
      Remove randomness from port assignment during coverage collection. (#7548) · 3f1d6d3b
      Ian Hickson authored
      Also, defer to test package for throttling (this will require a test
      package update as well).
      
      Also, add a lot more instrumentation to --verbose mode for tests, and
      fix minor trivial things here and there, and add error handling in
      more places.
      
      Also, refactor how coverage works to be simpler and not use statics.
      3f1d6d3b
  13. 12 Jan, 2017 1 commit
    • Todd Volkert's avatar
      Fix race condition in coverage collection (#7455) · 4f9e5c8d
      Todd Volkert authored
      Previously, it was possible for the test harness to bail
      and the test runner to complete before the platform plugin
      triggered the collection of coverage data. This fixes the
      race condition such that the pending coverage collection
      task is recorded immediately after starting the process.
      4f9e5c8d
  14. 09 Jan, 2017 1 commit
  15. 07 Jan, 2017 1 commit
    • Todd Volkert's avatar
      Update flutter_tools to use package:file throughout (#7385) · 8bb27034
      Todd Volkert authored
      This removes direct file access from within flutter_tools
      in favor of using `package:file` via a `FileSystem` that's
      accessed via the `ApplicationContext`.
      
      This lays the groundwork for us to be able to easily swap
      out the underlying file system when running Flutter tools,
      which will be used to provide a record/replay file system,
      analogous to what we have for process invocations.
      8bb27034
  16. 15 Dec, 2016 1 commit
  17. 30 Nov, 2016 1 commit
  18. 14 Nov, 2016 1 commit
    • Dan Rubel's avatar
      Refactor flutter command exit code - part 3 of 3 (#6838) · 34e466f1
      Dan Rubel authored
      * Remove the workaround that pinned args to v0.13.6
      This reverts most of the changes in commit 6331b6c8
      * throw exception if exit code is not an integer
      * rework command infrastructure to throw ToolExit when non-zero exitCode
      * convert commands to return Future<Null>
      * cleanup remaining commands to use throwToolExit for non-zero exit code
      * remove isUnusual exception message
      * add type annotations for updated args package
      34e466f1
  19. 03 Nov, 2016 1 commit
    • Devon Carew's avatar
      Better progress (#6677) · fcfb2a5c
      Devon Carew authored
      * make showElapsedTime default to true
      
      * support nested progresses
      
      * improve hot reload message
      
      * rethrow
      fcfb2a5c
  20. 22 Sep, 2016 1 commit
  21. 16 Sep, 2016 1 commit
    • Dan Rubel's avatar
      Refactor flutter command execution (#5892) · 18212382
      Dan Rubel authored
      * refactor _run to runCmd
      
      * replace requiresProjectRoot getter with call to commandValidator
      
      * replace requiresDevice getter with call to findTargetDevice
      
      * trace command requires a debug connection, not a device
      
      * inline androidOnly getter
      
      * rename command methods to verifyTheRunCmd and runCmd
      
      * move common verification into BuildSubCommand
      
      * rename deviceForCommand to device
      
      * rename methods to verifyThenRunCommand and runCommand
      18212382
  22. 27 Jul, 2016 1 commit
  23. 28 Jun, 2016 1 commit
  24. 24 Jun, 2016 2 commits
  25. 22 Jun, 2016 1 commit
  26. 14 Jun, 2016 1 commit
    • Ian Hickson's avatar
      Lock flutter tool while updating artifacts (#4476) · f92f71fe
      Ian Hickson authored
      This prevents multiple simultaneous runs of the analyzer from stomping
      over each other (e.g. multiple runs of 'update-packages'). Certain
      long-lived commands (like analyze, run, logs) are exempted once they've
      done enough work to be safe from most stomping action.
      
      This still doesn't make us entirely safe from craziness, e.g. if you're
      half way through an 'update-packages' run and you call 'git pull', who
      knows what state you'll end up in. But there's only so much one can do.
      
      Fixes https://github.com/flutter/flutter/issues/2762
      f92f71fe
  27. 13 Jun, 2016 1 commit
  28. 07 Jun, 2016 1 commit
    • Devon Carew's avatar
      add a restart command to the daemon protocol (#4385) · 3ba17136
      Devon Carew authored
      * refactor the --resident run option into a separate file
      
      * update daemon to run --resident apps
      
      * re-plumbing daemon start
      
      * send app logs
      
      * update tests
      
      * review changes
      
      * fix test runner
      
      * remove PackageMap.createGlobalInstance; rely on the ctor
      
      * review comments
      3ba17136
  29. 19 May, 2016 1 commit
  30. 17 May, 2016 1 commit
    • Ian Hickson's avatar
      Fix tests (#3977) · f284c1a0
      Ian Hickson authored
      Also, make sure that broken tests actually break the bots.
      
      And add a test to make sure that keeps happening.
      f284c1a0
  31. 12 May, 2016 1 commit
  32. 04 May, 2016 1 commit
  33. 18 Apr, 2016 1 commit
  34. 14 Apr, 2016 1 commit
    • Devon Carew's avatar
      run pub for analyze and test (#3310) · b172dd5a
      Devon Carew authored
      * run pub for analyze and test
      
      * don't run pub when doing repo analysis
      
      * move logic for when to run pub into the commands
      
      * re-write ternary expression
      b172dd5a
  35. 28 Mar, 2016 1 commit
  36. 25 Mar, 2016 1 commit
  37. 14 Mar, 2016 1 commit
  38. 12 Mar, 2016 1 commit