Skip to content

Conversation

kotlarmilos
Copy link
Member

Temporarily reverts #116907 due to #117714

@github-actions github-actions bot added the area-codeflow for labeling automated codeflow label Jul 17, 2025
@kotlarmilos kotlarmilos added the os-ios Apple iOS label Jul 17, 2025
@kotlarmilos kotlarmilos added this to the 10.0.0 milestone Jul 17, 2025
@kotlarmilos
Copy link
Member Author

/azp run runtime-extra-platforms

Copy link
Contributor

Tagging subscribers to 'os-ios': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kotlarmilos kotlarmilos enabled auto-merge (squash) July 17, 2025 14:33
@kotlarmilos
Copy link
Member Author

We have two options regarding failures reported in #117714.

  1. Merge this change, and live with the failures until the engineering team fixes the iOS/tvOS queues. Proceeding with the reverted xharness version would require waiting on scouting queues to be fixed, to start working on fixes.
  2. Use the new xharness version and fix the --username parameter on devices and timeout problem on simulators. Proceeding with the current xharness version would require us to fix device and simulator failures upfront on extra-platforms, but it would prepare us for transitioning to macOS 15.x.

Neither option is ideal. The key question is where we want to resolve these issues — in extra-platforms or in the xharness repository. Given that the scouting queues are currently not functional, and fixing the iOS/tvOS queues mitigates the failures for both xharness versions, I’m inclined to keep this PR open and try to fix the issues directly within extra-platforms -- at least until we get confirmation that the scouting queues are functional again.

Looking for opinions here. @akoeplinger @lewing @steveisok @vitek-karas

@vitek-karas
Copy link
Member

I slightly prefer the second option. In either case the state of the CI is not ideal, and the second option seems to give us faster path to resolution - or at least partial resolution.

@kotlarmilos
Copy link
Member Author

The CI is much cleaner now. One machine is still failing due to #117804. The engineering team is aware and working on it.

Follow-up steps:

auto-merge was automatically disabled July 24, 2025 08:24

Pull request was closed

@kotlarmilos kotlarmilos deleted the revert-116907-darc-main-dcd65c0b-9dcb-41e8-87d2-e1538e21e5ac branch July 24, 2025 08:24
@github-actions github-actions bot locked and limited conversation to collaborators Aug 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-codeflow for labeling automated codeflow os-ios Apple iOS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants