xcbeautify icon indicating copy to clipboard operation
xcbeautify copied to clipboard

xcbeautify hangs virtual machine on bitrise.io

Open pappalar opened this issue 2 years ago • 2 comments

Hello!

I am sorry I can't provide many more debug details. We are using bitrise with fastlane and xcbeautify to run our iOS builds.

all of our builds had extreme High CPU usage, and UI tests were getting completely stuck.

We checked the Bitrise VMs with a VNC and by checking the activity monitor we realized the cause of the freeze was the xcbeautify consuming all resources.

This is not causing a hang on our local machine, it's more tied to a VM environment.

Do you have any performance issue report regarding similar issues? or any way we can enable some performance logs/monitoring for improving this report? thanks

pappalar avatar Mar 28 '22 13:03 pappalar

note: removing xcbeautify solves the problem in our builds since the CPU usage does not spike

pappalar avatar Mar 28 '22 13:03 pappalar

We are experiencing the same issue. Calling fastlane's scan action passing it build_for_testing: true causes compile time to skyrocket. Compiling a single file takes 2-3 seconds.

itskoBits avatar Apr 05 '22 07:04 itskoBits

+1 to build time increasing when using scan and build_for_testing: true, we saw a 3x increase in build time, using jenkins with metal agents.

nicolasrostan avatar Feb 18 '23 01:02 nicolasrostan

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable. If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future. Thank you for your understanding.

github-actions[bot] avatar Jul 05 '23 02:07 github-actions[bot]

Hola 👋,

We want to inform you that we have decided to close this stale issue as there hasn't been any activity or response regarding it after marking it as stale.

We understand that circumstances may have changed or priorities may have shifted, and that's completely understandable. If you still believe that this issue needs to be addressed, please feel free to reopen it and provide any necessary updates or additional information.

We appreciate your understanding and look forward to your continued contributions to the project.

Thank you.

github-actions[bot] avatar Jul 10 '23 02:07 github-actions[bot]