xcpretty not printing any compilation step when <compilation mode = whole module> in swift

[acecilia]

Hi:

When running xcodebuild archive ... | xcpretty in my build server I realised that the build was spending a lot of time in the step Running script [CP] Check Pods Manifest.lock. After googling, I found this issue in cocoapods, which made me compare the raw xcodebuild output VS the xcpretty output.

When doing that, I realised that xcpretty was not printing any Compiling fileName.swift statements. After googling a bit more, I found this issue in xcpretty, suggesting that such an output does not happen when compilation mode = whole module, which is exacly my case, as I am archiving a release configuration.

In the end, what I conclude is that all the time spent on Running script [CP] Check Pods Manifest.lock is in reality compilation time, but it is not printed by xcpretty. Is this correct? Would it be possible to print something like "Compiling module - not printing compilation of individual files due to whole module optimization"?

Thanks

[daveluong]

Bump this up as we're facing the same issue. CircleCI actually kills the build job if there is no output for too long

[momoohidayat]

still had this issue, Running script '[CP] Check Pods Manifest.lock'

INFO [2020-08-06 15:38:03.25]: ▸ Running script '[CP] Check Pods Manifest.lock'
INFO [2020-08-06 15:42:18.37]: ▸ 2020-08-06 15:42:18.358 xcodebuild[87864:21122630]

takes 4-5min for this step

[mccarron]

Want to bump this as we have this issue and took a long time to figure out it was coming from XCPretty on Fastlane.

In our case it was having long pauses (~15min for our project) after this step:

INFO [2021-03-02 21:02:28.28]: ▸ Processing Info.plist

Which doesn't help at all but see a lot of people seeing this pause on CI on various Github issues and having their jobs time out. So hopefully searching they'll find it's this by adding my reply as well.

We extended build time for now, but may do Release builds with disable_xcpretty: true set going forward. It's uglier to read but will not fail if a build takes a long time to optimize.