search

bitrise-steplib / steps-cocoapods-install

MIT License
23 stars 18 forks source link

Step never fails after `Analyzing dependencies` timeout [Business critical] #81

Closed Ariandr closed 2 years ago

Ariandr commented 2 years ago

Troubleshooting

Issue description

If the Analyzing dependencies goes into timeout, the step doesn't fail and the build never stops. It happened only once for me, but I imagine if the app was on the Credits system and they ran out because of non-stopping build, it would have caused a business issue (money waste).

Bitrise info

Installing Pods
$ pod "_1.11.2_" "install" "--no-repo-update"
Analyzing dependencies
timeout after 5400 seconds

Steps to reproduce

The issue cannot be reliably reproduced because the timeout happens rarely. But in case it happens, the build should fail immediately.

Screenshot at Nov 09 16-12-53

image

Screenshot at Nov 09 16-13-42
Roland-Bak commented 2 years ago

Hello there @Ariandr 👋

Can you let me know if this issue still persists on the new Xcode 13.1 stack? If it does, could you please enable Support Access for your app so we can compare builds and try to pinpoint the possible reason why this happens? 🙂

Ariandr commented 2 years ago

Hi @Roland-Bak

Can you let me know if this issue still persists on the new Xcode 13.1 stack? It cannot be reproduced in 99% of cases, so it's impossible to tell. But since it depends on Cocoapods only and this step, it will happen on any Xcode version stack.

It's clearly the issue with the lack of handling of Cocoapods Analyzing dependencies timeout.

bitrise-coresteps-bot commented 2 years ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

Ariandr commented 2 years ago

The issue must be checked.

Roland-Bak commented 2 years ago

Hello there @Ariandr 👋

I wanted to let you know that we are currently looking into the possibility of builds hanging at various parts of the workflow, and this issue seems to be one of those. The investigation is on the way, and although it has prerequisites that need to be in place in order to progress, as soon as there is a progress, we'll let you know.

I also wanted to mention that in case someone is on a credit based plan and has a timeout issue, we will refund the credits that were spent on a hanged build so that they can use it towards better ends.

Hope this helps! 🙂

bitrise-coresteps-bot commented 2 years ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

bitrise-coresteps-bot commented 2 years ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.