-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode 11.3 validation issues #12
Xcode 11.3 validation issues #12
Comments
Currently the code attempts to validate runtimes, which can get thrown off in a few scenarios. By deferring to `xcodebuild` / Apple to validate options, it's easier to maintain the xctestrunner Fixes: google#12
Currently the code attempts to validate runtimes, which can get thrown off in a few scenarios. By deferring to `xcodebuild` / Apple to validate options, it's easier to maintain the xctestrunner Fixes: google#12
Currently the code attempts to validate runtimes, which can get thrown off in a few scenarios. By deferring to `xcodebuild` / Apple to validate options, it's easier to maintain the xctestrunner Fixes: google#12
Currently the code attempts to validate runtimes, which can get thrown off in a few scenarios. By deferring to `xcodebuild` / Apple to validate options, it's easier to maintain the xctestrunner Fixes: google#12
Thanks for reporting that. The root cause is xctestrunner used the command output of Why we are doing this validation is |
When I run xctestrunner on Xcode 11.3 I get the following error:
When I add
13.3
to the test runner rule, underos_version
I get:When I add
13.2
to the test runner rule, underos_version
I get:After reading the
rules_apple
documentation, I suspected theos_version
means simulator runtime.It seems like there is confusion between the SDK version Bazel is using, and the runtime version that rules_apple is using. Perhaps this is out of scope of the test runner, as
os_version
is determined by rules_apple, Bazel.The text was updated successfully, but these errors were encountered: