Xcode Server Build Service Issues

Question

Created Jun ’16

Replies 3

Boosts 0

Views 5.1k

Participants 3

I have been facing this issue for more than a year now and it is still weird and annoying. My temporary fix was to disable Tests on my Xcode Bot but continuous integration without tests is almost pointless.

This is about an Xcode Bot for an OS X App. If I enable Perform test action, once in a while it will succeed and produce both .app.zip and .xcarchive which I can download, this is what I want to happen all the time. But all the time, right after it did succeed once, integrations will get stuck on step 5 of 9, as you can see in this screenshot : [img not appearing]

...and eventually will look like this : [img not appearing]

"Build Service Error Running task was terminated because it produced no activity for more than 600 seconds (use sudo xcrun xcscontrol --configure-integra..."

"Build Service Error The xcodebuild task completed with uncaught signal (status 15)"

I tried to run the suggested command but it won't change anything.

Looking deeper in the logs, here is what's happening :

EF8F58972E2C) Test bundle is ready, running protocol 16, requires at least version 8. IDE is running 16 and requires at least 8
Sampling process 72199 for 10 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Sample analysis of process 72199 written to file /Library/Developer/XcodeServer/Integrations/Integration-37e7cb91cd7dc3282ace0ecea7060394/72199.sample
sample[76512]: sample cannot find any existing process you have access to which has a name like 'Interface Builder Cocoa Touch Tool'; try running with `sudo`.
sample[76513]: sample cannot find any existing process you have access to which has a name like 'ibtool'; try running with `sudo`.
sample[76514]: sample cannot find any existing process you have access to which has a name like 'ibtoold'; try running with `sudo`.
** BUILD INTERRUPTED **

This is the same issue this guy is having http://stackoverflow.com/questions/33907543/xcode-server-ibtool-build-failures

Thanks for your help.

Boost

Answer 1

Apple Staff OP

Apple

Jun ’16

Xcode Server has a limit of 10 minutes on builds it thinks have stalled. Typically, this means that your build or test hasn't reported any output in that timeframe.

A few questions:

- Do you have a long running test in your project?

- Are you using code signing (if so, what configuration)?

- There's a flag you can pass to xcscontrol (sudo xcrun xcscontrol --configure-integration-timeout SECONDS) to increase this timeout.

A.

0

Answer 2

quentinf OP

Jun ’16

The build and test aren't doing anything, so

- No to your first question, there isn't a long running test.

- I am not quite sure about the code signing I should try other options: it currently is on Mac App Store and the server has one developer's private key added to the System.keychain

- I don't think I need to increase the timeout, instead I would like the server to realize much earlier that something's wrong if there is a code signing issue.

0

Answer 3

reststopatintel OP

Jul ’16

I am having the same issue, but we are also seeing it happen during checkout or some spurious point in the xcodebuild after only a few minutes.

(Unfortunately there are no actual timestamps in the logs which are useful, and when the logs are moved into the IntegrationAssets directory, they are all updated, losing any last add or initial creation dates on the files themselves).

In our case, our project often gets ** BUILD INTERRUPTED ** during the create user-installable product.

We notice that the bot is generating 15 separate IPA files which takes a long time for some reason.

The FIX for this is to add additional time:

sudo xcrun xcscontrol --configure-integration-timeout SECONDS

where for us, SECONDS is now 3900 (an hour and 5 minutes, which by itself is ridiculous*), and we got the error 2 times in the past 4 days.

* ridiculous -- there is a lot of output in the logs, and in no case is it idle for an hour, so the timeout must be from the start of integration, and something is not re-setting the "no output" flag at the beginning of each compile/analyze/etc phase.

We are also seeing this error well before the actual timeout time. We've gotten it during checkout from the repository (which is generating lots of output), and (of course) during the build, which currently takes between 8 and 12 minutes. (With the timeout set to 3600 or 3900, 8-12 minutes is well less than that).

Clearly something is sending this signal pre-maturely.

Does anyone know if the (status 15) happens to be the unix signal 15 -- SIGTERM -- or is it something else?

0