Skip to content
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

Run all flutter/engine macOS tests manually on macOS 14.5 bot #148877

Closed
1 task done
Tracked by #148870 ...
vashworth opened this issue May 22, 2024 · 3 comments
Closed
1 task done
Tracked by #148870 ...

Run all flutter/engine macOS tests manually on macOS 14.5 bot #148877

vashworth opened this issue May 22, 2024 · 3 comments
Assignees
Labels
P2 Important issues not at the top of the work list team-ios Owned by iOS platform team triaged-ios Triaged by iOS platform team

Comments

@vashworth
Copy link
Contributor

vashworth commented May 22, 2024

Prerequisites

Instructions

Update to latest depot_tools by running gclient:

For each macOS engine test, you have to run the sub-builds individually. Using test/orchestrator Linux linux_web_engine as an example:

  1. Open https://ci.chromium.org/ui/p/flutter/builders/luci.flutter.prod/Linux%20linux_web_engine
  2. Click the top build
  3. Ensure build is for main branch (Under the Infra tab, check git_branch under "Input Properties" section)
  4. Check what sub-builds use macOS
  5. Copy sub-build BuildbucketID
    Screenshot 2024-05-22 at 11 50 56 AM
  6. Run led get-build "[insert BuildbucketID]" > properties.json
  7. Replace the following in the properties.json:
    • "bucket": "prod.shadow", -> "bucket": "staging.shadow",
    • "shadowed_bucket": "prod" -> "shadowed_bucket": "staging"
    • "service_account": "flutter-prod-builder@chops-service-accounts.iam.gserviceaccount.com" -> "service_account": "flutter-staging-builder@chops-service-accounts.iam.gserviceaccount.com"
    • "value": "luci.flutter.prod" -> "value": "luci.flutter.staging"
  8. Run cat properties.json | led edit-recipes-bundle | led launch

File issues for tests that fail and add links to the issues in #148882. This is important so we can track any fixes that need to be cherrypicked to beta/stable and so steps that are steps are not completed before issues are resolved.

@vashworth vashworth added P2 Important issues not at the top of the work list team-ios Owned by iOS platform team triaged-ios Triaged by iOS platform team labels May 22, 2024
@vashworth vashworth changed the title Run all flutter/engine tests on macOS 14 bots Run all flutter/engine macOS tests manually on macOS 14 bot May 22, 2024
@vashworth vashworth self-assigned this May 28, 2024
@vashworth vashworth changed the title Run all flutter/engine macOS tests manually on macOS 14 bot Run all flutter/engine macOS tests manually on macOS 14.5 bot May 28, 2024
@vashworth
Copy link
Contributor Author

vashworth commented May 30, 2024

Tracking Progress:

@vashworth
Copy link
Contributor Author

Ran and verified all tests pass.

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P2 Important issues not at the top of the work list team-ios Owned by iOS platform team triaged-ios Triaged by iOS platform team
Projects
None yet
Development

No branches or pull requests

1 participant