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

Xcode cache path not set correctly sometimes in recipes #141398

Closed
vashworth opened this issue Jan 11, 2024 · 5 comments
Closed

Xcode cache path not set correctly sometimes in recipes #141398

vashworth opened this issue Jan 11, 2024 · 5 comments
Assignees
Labels
P1 High-priority issues at the top of the work list team-infra Owned by Infrastructure team triaged-infra Triaged by Infrastructure team

Comments

@vashworth
Copy link
Contributor

Type of Request

bug

Infrastructure Environment

Recipes

What is happening?

Devicelab has a different Xcode cache path than chromium bots.

In devicelab, the path is /opt/flutter/xcode. In non-devicelab, the path is self.m.path['cache'].join(_XCODE_CACHE_PATH).

In a number of places in https://flutter.googlesource.com/recipes/+/refs/heads/main/recipe_modules/osx_sdk/api.py, we use the _XCODE_CACHE_PATH regardless of it's a devicelab bot or not. Search for _XCODE_CACHE_PATH and you'll find places it's used. We should fix this.

Probably best solution would be to have the path come from a function like the example below and remove _XCODE_CACHE_PATH to prevent confusion.

def _xcode_cache_path(devicelab):
  if devicelab:
      return '/opt/flutter/xcode'
  return self.m.path['cache'].join('osx_sdk')

Steps to reproduce

No response

Expected results

No response

@vashworth vashworth added the team-infra Owned by Infrastructure team label Jan 11, 2024
@vashworth
Copy link
Contributor Author

cc @ricardoamador I noticed this because looks like the Cache Micro Manager uses the wrong path for devicelab

@ricardoamador
Copy link
Contributor

@vashworth thanks for finding this. Will look into it.

@ricardoamador ricardoamador added P1 High-priority issues at the top of the work list triaged-infra Triaged by Infrastructure team labels Jan 11, 2024
@ricardoamador
Copy link
Contributor

Hmm I see, there is some confusion with the assumptions made in the code. You are right that we are using the wrong cache path in the cache micro manager and possibly elsewhere. Code needs some cleanup and clarification in the documentation.

@ricardoamador
Copy link
Contributor

Fix for this has landed and has been running without issues across mac tasks.

Copy link

github-actions bot commented Feb 5, 2024

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 Feb 5, 2024
XuanTung95 pushed a commit to XuanTung95/recipes that referenced this issue Feb 14, 2024
Commenting out the call to the cache_micro_manager as there are still some typing errors happening under the covers. But this is lower priority than fixing the path issues.

Reland of this: https://flutter-review.googlesource.com/c/recipes/+/54122

Proof:
Devicelab test: https://ci.chromium.org/ui/p/flutter/builders/prod.shadow/Mac_ios%20animated_advanced_blend_perf_ios__timeline_summary/13/overview
Non devicelab test: https://ci.chromium.org/ui/p/flutter/builders/prod.shadow/Mac%20customer_testing/1/overview

Fixes: flutter/flutter#141398
Change-Id: I41eb01e0bbe101d9ce7f0b0deadfa432c8126fd3
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/54222
Reviewed-by: Keyong Han <keyonghan@google.com>
Commit-Queue: Ricardo Amador <ricardoamador@google.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 High-priority issues at the top of the work list team-infra Owned by Infrastructure team triaged-infra Triaged by Infrastructure team
Projects
None yet
Development

No branches or pull requests

2 participants