mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
bb306c53a3
Xcode is in some kind of half-installed state (missing a cert? unknown)
on some devicelab Macs https://github.com/flutter/flutter/issues/161655.
As of https://github.com/flutter/flutter/pull/163685 Xcode cipd
installation isn't requested as part of the builder configuration, so it
seems like Xcode is just hanging out on that devicelab bot
quasi-installed, unrelated to the recipe.
In any case, the tool is actually doing the right thing and detecting
that Xcode isn't in a good state and continuing as if it isn't
installed, but is logging a wall of error text about it to stderr, which
that Android test doesn't like. Instead of updating the test to allow
stderr, instead swap the Xcode installation path to `exitsHappySync` to
only check the exit code (or exception), which is the original intention
behind the Xcode command line checks.
|
||
|---|---|---|
| .. | ||
| application_package_test.dart | ||
| cocoapod_utils_test.dart | ||
| cocoapods_test.dart | ||
| cocoapods_validator_test.dart | ||
| darwin_dependency_management_test.dart | ||
| macos_device_test.dart | ||
| macos_ipad_device_test.dart | ||
| macos_project_migration_test.dart | ||
| macos_workflow_test.dart | ||
| swift_package_manager_test.dart | ||
| swift_packages_test.dart | ||
| xcode_test.dart | ||
| xcode_validator_test.dart | ||