Skip to content

Allow iOS simulator runtimes to be set from .ci.yaml #99698

Closed
flutter-team-archive/engine
#31915

Description

@jmagman

It's now possible to run different tests with different iOS runtimes #91689. Expose this as a settable property in .ci.yaml.
This is needed before the engine builders can migrate to Xcode 13. #94078

Activity

  1. added
    team-infraOwned by Infrastructure team
    P1High-priority issues at the top of the work list
    on Mar 7, 2022
  2. self-assigned this
    on Mar 7, 2022
  3. yusuf-goog commented on Mar 8, 2022

    @yusuf-goog
    Contributor

    https://flutter-review.googlesource.com/c/infra/+/27742 adds getting "runtime_versions" property value from ci.yaml into osx_sdk property in recipes.

  4. jmagman commented on Mar 9, 2022

    @jmagman
    MemberAuthor

    So I tried this in flutter-team-archive/engine#31915 and it doesn't seem to be pulling in both runtimes.
    .ci.yaml:

          runtime_versions: >-
            [
              "ios-13",
              "ios-15"
            ]
    

    But I don't see the expected install xcode runtime ios-13-0, Removing stale iOS 13.0.simruntime, Moving ios-13-0 to final dest steps (see led run https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/magder_google.com/15ce71ff15e962e13bb340538339f307495e846c6eba7ec007621015430e011f/+/build.proto for example).

    And the list simulators step only shows iOS 15:

    == Runtimes ==
    iOS 15.0 (15.0 - 19A339) - com.apple.CoreSimulator.SimRuntime.iOS-15-0
    == Devices ==
    -- iOS 15.0 --
    

    https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8820208992595983441/+/u/list_simulators/stdout

  5. yusuf-goog commented on Mar 10, 2022

    @yusuf-goog
    Contributor

    flutter/cocoon#1652 adds the functionality for presubmit.

  6. yusuf-goog commented on Mar 10, 2022

    @yusuf-goog
    Contributor

    Builds are now picking up the properties as expected.

  7. github-actions commented on Mar 24, 2022

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  8. locked as resolved and limited conversation to collaborators on Mar 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listteam-infraOwned by Infrastructure team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions