How to investigate Timed Out issue for a SPI build

[Kyle-Ye]

I'd like to fix some of the SPI build issue. But of the builds just show "Time Out" without any log information.

eg. https://swiftpackageindex.com/OpenSwiftUIProject/OpenSwiftUI/builds

[finestructure]

When a build times out, it exceeds the 10 minutes we budget for the build processing. That includes

• checking out the repository
• resolving packages
• building the project
• generating documentation (if applicable)
• uploading the doc archives to S3 (if applicable)

There's much to report back in terms of logs and running the steps locally should give you a good idea how this will take. Our build machines are not super fast but they're not slow, either. (Apple builds are un on M1s, Linux builds on a decent size Linux.)

I hope that helps!

[Kyle-Ye]

I can build it fine locally with the iOS build within a very short time.(The time should be almost the same with the macOS build). So I was wondering which step is wrong on the CI so that I can fix it.

There's much to report back in terms of logs and running the steps locally should give you a good idea how this will take.

Is there any way I can reproduce it locally since I do not know the build command CI is using and what env it will inject. A command with env or log will really be helpful here.

[finestructure]

I that case it might have been a one-off build system issue. I've re-triggered the timed out builds.

[Kyle-Ye]

Hi, thanks for the update. Still timing out unfortunately. @finestructure
I'm worried this might not be a simple timeout - could be something causing the build to hang. Any chance we could get the build logs to debug this?
Alternatively, it might just be that the package genuinely takes >10 minutes on M1. I have an M1 device here - if you can tell me from the logs whether it's a Debug or Release build, I can test locally and time it.
This would help us figure out if we need to:

• Investigate and fix a potential infinite loop or hanging condition
• Optimize the build steps for my package (e.g., if the build step already takes 8 minutes, given the current 10min budget, I'd choose not to build documentation on SPI, but at least SPI could help confirm the build matrix across platforms)

[Kyle-Ye]

Just noticed something interesting - SPM + macOS builds are passing fine, but both Xcodebuild + iOS and Xcodebuild + macOS are timing out.
This suggests another possibility: Xcodebuild might be significantly slower than SPM under the current configuration. Could be worth comparing the build times between SPM and Xcodebuild for the same target to see if there's a performance regression with Xcodebuild specifically.
Can I know which Xcode version SPI is current using for the iOS configuration?

[finestructure]

We should be switched to the release version of Xcode 26 soon. Let's see if that fixes things!