Skip to content

Move mac_ios tests from staging to prod #73392

Closed

Description

@godofredoc

DeviceLab mac ios tests have been running and passing consistently for a few weeks now. We will start moving them to prod with the following steps:

  • Move flutter_ios_staging.py bot config file to prod by copying it to flutter_ios.py.
  • Add mac 6,7,8 and 11 to flutter staging pool.
  • Request 10 mac machines from the fuchsia ops to replace old machines.
  • Wait for salt configurations to propagate from staging to prod.
  • Move all the test beds from the staging pool to prod.
  • Move all the tests to the flutter infra prod devicelab configuration.

Activity

  1. self-assigned this
    on Jan 6, 2021
  2. godofredoc commented on Jan 7, 2021

    @godofredoc
    ContributorAuthor

    There is a problem with salt states: @yusufm is looking at that problem

  3. yusufm commented on Jan 8, 2021

    @yusufm
    Contributor

    The line of template code in the sls file that gets the gid for the group runs first. Which means that the group doesn't yet exist (since its created in that sls file itself), so it fails. We need to ensure that the group is created first before this code runs.

  4. godofredoc commented on Feb 11, 2021

    @godofredoc
    ContributorAuthor

    We also need to use fixed installations of xcode to remove the 10+ minutes overhead when the caches are cold.

  5. godofredoc commented on Mar 1, 2021

    @godofredoc
    ContributorAuthor

    This is complete.

  6. github-actions commented on Aug 5, 2021

    @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.

  7. locked as resolved and limited conversation to collaborators on Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

team-infraOwned by Infrastructure team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions