Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@christopherfujino
Copy link
Contributor

@christopherfujino christopherfujino commented Jul 14, 2021

for the most part, brought this in sync with the ToT .ci.yaml, minus Linux Benchmarks and some runIf fields.

Related to #27415
Part of flutter/flutter#86566

@flutter-dashboard
Copy link

This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter.

Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed.

@google-cla google-cla bot added the cla: yes label Jul 14, 2021
Copy link
Contributor

@CaseyHillers CaseyHillers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - Thanks for updating the releases with this

.ci.yaml Outdated
{"name":"builder_mac_engine","path":"builder"}
]
os: Mac-10.15
xcode: "11e708" # Xcode 12
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this need to explicitly be a string? Shouldn't it be loaded as a json string anyways?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a pre-submit ci.yaml validation error. I think a value that starts with an integer is assumed to be a number, and then the e made it a parse error? Using this https://www.convertjson.com/yaml-to-json.htm I get 11e708 -> null

Copy link
Contributor Author

@christopherfujino christopherfujino Jul 15, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll give github credit, they have a yaml syntax coloring in their diff view, and the 11e708 was a different color than the strings. I don't know the yaml parse rules, but apparently github does :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, it's actually 11e708 is parsed as a number in scientific notation.

@chinmaygarde
Copy link
Member

The CI failures look related.

@christopherfujino christopherfujino changed the title [flutter_releases] update .ci.yaml and pin xcode to 12 [flutter_releases] update .ci.yaml and pin xcode to 11 Jul 15, 2021
@christopherfujino
Copy link
Contributor Author

Should probably apply this fix #27454

@CaseyHillers
Copy link
Contributor

You'll need to rebase with tip of tree to fix the failing checks

@christopherfujino
Copy link
Contributor Author

You'll need to rebase with tip of tree to fix the failing checks

You mean tip of .ci.yaml? Is cocoon actually parsing these properties?

@CaseyHillers
Copy link
Contributor

You mean tip of .ci.yaml? Is cocoon actually parsing these properties?

No, I forgot this is a release cherry-pick :-) Carry on, i'm not sure how we fix these tips of issues (or if we just ack them)

@christopherfujino
Copy link
Contributor Author

closing in favor of: #27487

@jmagman
Copy link
Member

jmagman commented Jul 20, 2021

@christopherfujino did you mean to close this?

@christopherfujino
Copy link
Contributor Author

@christopherfujino did you mean to close this?

Yes, #27487 includes all of these changes, plus this fix.

@christopherfujino
Copy link
Contributor Author

Oh, nvm, i see what you mean :P

@christopherfujino christopherfujino deleted the cherrypicks-flutter-2.4-candidate.4 branch July 20, 2021 17:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants