sangeeths03
sangeeths03
Hi @andrewclaus, I was able to successfully reproduce the issue. Starting from image version 20250408.1132, the SwiftLint version was upgraded to 0.59.0. I also tested this with 0.59.1, and both...
Hi @andrewclaus ,Just checking in—since this issue is due to changes in the newer SwiftLint versions (not the runner) , are we okay to close this issue?
Hi @andrewclaus, As we discussed earlier, the issue you're seeing is caused by recent SwiftLint versions 0.59.0 and 0.59.1, which have dropped support for duplicate keys in configuration files. This...
Hi @SpecLad , We are sorry to inform you that at this point in time, it is difficult to add this tool to our images. Having said that we will...
Hi @jiasli, the expected version (2.72.0) is now included in the current week's macOS image generation. Following deployment, this version will be available across all macOS images.
@jiasli All macOS images, except for macOS-14-arm, have been updated to Azure CLI version 2.73.0. The macOS-14-arm image will also include the new version once its deployment is complete.
@jiasli Now the latest version 2.73.0 is available across all macOS runners.
Hi @mboudreau, @grzegorzkrukowski Thanks for the detailed report and repro steps! I created a test workflow based exactly on your suggestions to reproduce the AppleEvent timed out error on both...
Hi @austinmatherne-wk , from your workflow i created a minimal workflow and it's working fine (https://github.com/sangeeths03/runner-images-sangeeth/actions/runs/15991196857). I'll dig deeper into this and continue investigating the underlying cause. Appreciate the reference...
Hi @mboudreau, @grzegorzkrukowski, @kjxbyz, and @austinmatherne-wk — the workflow appears to be running fine now. Could you please also confirm on your end? If everything looks good, we can go...