Xcode Bot integration error: crash in mmap

Question

I don’t know how to fix this Build Service Error error when I try to integrate the Xcode bot in OS X Server 4.0.

Everything works fine on this server, I even have another working bot in a different branch of the same project.

He is leaving me

Release Error: Error. Build service error. Error: mmap error. Could not write data: Invalid argument (-1).

I do not know what to do...

Thanks in advance!

Answer 1

This is apparently due to a bug in Xcode 6.1.1 . To workaround, I reinstalled Xcode 6.1 .

I couldn’t just select a different version of Xcode in the Server application, I had to completely reset the Xcode service ( remove all your bots , you have to recreate them):

sudo xcrun xcscontrol --reset 

Before I could select Xcode 6.1 in the Server application, I also had to run this command:

 sudo xcrun xcscontrol --initialize 

If someone feels very adventurous and wants to understand the root cause of the problem on Xcode 6.1.1, this is where the error comes from. The binary file libgit2 is located in /Xcode-6.1.1.app/Contents/Developer/usr/lib/libgit2.dylib

Answer 2

I had the same problem and I just updated the bot without making any changes to fix it. Just go to the report navigator in Xcode, select your bot, click "Edit bot ..." and update it without making any changes.

Answer 3

Starting with version 6.3 (possibly earlier), Xcode now offers a “Fix” button that corrects the Git credentials and launches me. In the next build, there were warnings about the status of the working copy, but after cleaning, the next build was in order.

Answer 4

I had a little Finnish solution to this problem. Still not sure what causes the problem, but it was sporadically unsuccessful for me. What I did, I continued to integrate with the always clean set until I received a successful test, at that moment I edited the bot so that it would never clean. Now it successfully runs the tests every time. I am not saying that this is the right solution, and I know that this is not a good solution, but having tried resetting the osx server and updating my ssh keys, etc., This is the only way I could get around this.