-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
Mac test ignoring os
field on prod task, ran on newer version of macOS
#99087
Comments
I am afraid this is expected. For post-submit builders, their configs will be auto-rolled after it's merged. Let me double check. |
How long does it usually take to auto-roll, that config change happened 21 hours ago #98297 |
The culprit is here: https://flutter.googlesource.com/infra/+/refs/heads/main/config/lib/ci_yaml/ci_yaml.star#315 |
New os version is picked up: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20web_tool_tests/5037/overview, but it seems still using new xcode version.. |
@CaseyHillers IIRC, the properties will be merged among platform and target. Is the xcode version defined in target level expected to be auto rolled? |
It looks like It should pull from the merged _properties instead of the platform |
https://flutter-review.googlesource.com/c/infra/+/27420 to override with target level property. |
Changes populated, and test is validated to run on expected test beds. |
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 |
Mac web_tool_tests
ran on a macOS 12 machine, even though.ci.yaml
specifies Mac-10.15.flutter/.ci.yaml
Lines 3077 to 3078 in 37a1aaf
https://ci.chromium.org/p/flutter/builders/prod/Mac%20web_tool_tests/5034
https://chromium-swarm.appspot.com/task?id=5946338c72923b10&o=true&w=true
Task dimensions shows:
Note it failed due to #98278 which seems to only reproduce on macOS 12, which is how I noticed this.
The text was updated successfully, but these errors were encountered: