JP Simard

I've also filed an issue in SwiftPM, which can be easier to track for non-Apple folks than the feedback you filed: https://github.com/apple/swift-package-manager/issues/7098

Support has landed in SwiftPM: https://github.com/apple/swift-package-manager/pull/7167 Hopefully the _next_ minor Xcode release will include a toolchain with that. So 15.2 which according to past years release cadence should be expected...

The Linux CI job appears to be failing because it can't download the SwiftPM plugin binary artifact: > error: failed downloading 'https://github.com/realm/SwiftLint/releases/download/0.54.0/SwiftLintBinary-macos.artifactbundle.zip' which is required by binary target 'SwiftLintBinary': downloadError("Error...

I'm taking a look at parallelizing `XcodeProj.write()`.

Ah of course I should have thought to try setting the test target as a launch action instead of a test action. This works just fine: ```starlark xcodeproj( name =...

Feel free to close this issue, maybe all this needs really is documentation for how to run non-XCTest based test targets.

What would you suggest as next steps to dive deeper? Should I add `--toolchain_resolution_debug='@bazel_tools//tools/cpp:toolchain_type'` to our CI jobs or would that not yield helpful results?

> I imagine the core issue is the one we've seen in the past with github actions where the xcode discovery time takes so long that it ends up timing...

> My theory on that issue is that because it discovers every single installed Xcode version and the SDK versions for each one, on GitHub actions there are so many...

Yes, but the CI job is using that configuration.