mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
f92f71feb9
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
34 lines
1.1 KiB
Dart
34 lines
1.1 KiB
Dart
// Copyright 2015 The Chromium Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
import 'package:flutter_tools/src/android/android_sdk.dart';
|
|
import 'package:flutter_tools/src/commands/devices.dart';
|
|
import 'package:flutter_tools/src/device.dart';
|
|
import 'package:test/test.dart';
|
|
|
|
import 'src/common.dart';
|
|
import 'src/context.dart';
|
|
|
|
void main() {
|
|
group('devices', () {
|
|
testUsingContext('returns 0 when called', () {
|
|
DevicesCommand command = new DevicesCommand();
|
|
return createTestCommandRunner(command).run(<String>['list']).then((int code) {
|
|
expect(code, 0);
|
|
});
|
|
});
|
|
|
|
testUsingContext('no error when no connected devices', () {
|
|
DevicesCommand command = new DevicesCommand();
|
|
return createTestCommandRunner(command).run(<String>['list']).then((int code) {
|
|
expect(code, 0);
|
|
expect(testLogger.statusText, contains('No connected devices'));
|
|
});
|
|
}, overrides: <Type, dynamic>{
|
|
AndroidSdk: null,
|
|
DeviceManager: new DeviceManager()
|
|
});
|
|
});
|
|
}
|