Skip to content

Add version to xcode name cache.#99586

Merged
godofredoc merged 1 commit intoflutter:masterfrom
godofredoc:fix_caches
Mar 5, 2022
Merged

Add version to xcode name cache.#99586
godofredoc merged 1 commit intoflutter:masterfrom
godofredoc:fix_caches

Conversation

@godofredoc
Copy link
Contributor

Engine and Flutter using different xcode versions with the same cache
name is causing multiple problems when trying to find the runtimes. To
prevent this issue we will need to use different cache names for
different xcode versions.

Bug: #99429

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
  • I signed the CLA.
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Engine and Flutter using different xcode versions with the same cache
name is causing multiple problems when trying to find the runtimes. To
prevent this issue we will need to use different cache names for
different xcode versions.

Bug: #99429
@godofredoc godofredoc merged commit ea0b771 into flutter:master Mar 5, 2022
@godofredoc godofredoc deleted the fix_caches branch March 5, 2022 06:34
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 5, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 5, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 5, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 5, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 5, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 5, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 5, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 5, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 6, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 6, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 8, 2022
@jmagman
Copy link
Member

jmagman commented Mar 9, 2022

In retrospect I don't know why this worked given the engine cache name was already different old_osx_sdk
https://github.com/flutter/engine/blob/621c88dc2d133aea3fb52f78fc0f603a737b077f/.ci.yaml#L60

@godofredoc
Copy link
Contributor Author

In retrospect I don't know why this worked given the engine cache name was already different old_osx_sdk https://github.com/flutter/engine/blob/621c88dc2d133aea3fb52f78fc0f603a737b077f/.ci.yaml#L60

I believe this means we can't reuse named caches for different xcode versions. E.g we where using xcode_sdk for 12c33 and then we used the same name for 13a233. Do you remember if we were running builds with the two versions at any given point in time?

@jmagman
Copy link
Member

jmagman commented Mar 9, 2022

Do you remember if we were running builds with the two versions at any given point in time?

Some staging machines had to test it before it was merged. Other than that, no AFAIK. I guess it wasn't between the engine and framework at all, but between different framework machines that had different versions of Xcode cached before and after it was bumped? I don't know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants