flutter/dev/automated_tests/flutter_test
Ian Hickson f92f71feb9 Lock flutter tool while updating artifacts (#4476)
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
2016-06-14 10:16:08 -07:00
..
README.md Make it possible to run tests live on a device (#3936) 2016-05-16 12:53:13 -07:00
test_async_utils_guarded_expectation.txt Lock flutter tool while updating artifacts (#4476) 2016-06-14 10:16:08 -07:00
test_async_utils_guarded_test.dart Make it possible to run tests live on a device (#3936) 2016-05-16 12:53:13 -07:00
test_async_utils_unguarded_expectation.txt Lock flutter tool while updating artifacts (#4476) 2016-06-14 10:16:08 -07:00
test_async_utils_unguarded_test.dart Make it possible to run tests live on a device (#3936) 2016-05-16 12:53:13 -07:00

The files in this directory are used as part of tests in the flutter_tools package. They are here because here these tests need a pubspec.yaml that references the flutter framework (which is intentionally not true of the flutter_tools package).