Hello. what is the status of this issue? We are getting hit by it hard recently. An example of failed builds sequence, eventually fixed by stubborn Rebuilding: https://circleci.com/gh/kitt-browser/kitt/466
timed out in 467, success in 468
Please contact support about this and we’ll credit you for minutes used on these exit 65 failures. We’re still investigating the cause of these flakey failures, but we don’t want you paying extra for them.
I understand this must be terribly frustrating. We have people spending time trying to diagnose this (and have been looking at this for awhile unfortunately). It appears that Error Code 65 is a more generic error code which makes this diagnosis harder as it likely pertains to several possibly unrelated topics.
In our research, we’ve found that it appears to hit many OS X platforms (including complements and competitors). Because it’s increasingly common, we have tried to diagnose if hosting has a common cause. It appears to have started happening more since the last version of XCode as well. We feel a similar frustration ourselves as we continue to try and solve this.
My team recently shipped a change such that
you won’t be charged for the minutes spent where a build fails due to Error Code 65
We will auto-retry that build for you up to 3x (as we’ve seen repeatedly this bug can be intermittent).
It doesn’t solve the issue (I wish we could do that as easily!) but I hope it shows a sign of respect for your situation. Thanks for being CircleCI customers.
EDIT Jan 16 2017: We no longer recommend using UUIDs to start simulators. The OS X image has been updated to resolve the underlying issue, and using UUIDs is no longer necessary. Please check out this post for examples of how to choose the simulators by name.
this issue is for most people very likely caused by a timeout because the iOS simulator not starting fast enough.
A workaround that has been tested by us is starting the GUI simulator first with:
distiller-build-8:~ distiller$ xcrun instruments -w ‘A70FE3C7-756F-44BF-BE46-68663FAE2EE3’
2016-07-28 15:34:43.398 instruments[3140:14974] [MT] DVTSDK: Skipped SDK /Applications/Xcode-7.3.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk; its version (7.1) is below required minimum (9.3) for the iphonesimulator platform.
2016-07-28 15:34:43.399 instruments[3140:14974] [MT] DVTSDK: Skipped SDK /Applications/Xcode-7.3.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.4.sdk; its version (8.4) is below required minimum (9.3) for the iphonesimulator platform.
2016-07-28 15:34:43.399 instruments[3140:14974] [MT] DVTSDK: Skipped SDK /Applications/Xcode-7.3.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.0.sdk; its version (9.0) is below required minimum (9.3) for the iphonesimulator platform.
2016-07-28 15:34:43.400 instruments[3140:14974] [MT] DVTSDK: Skipped SDK /Applications/Xcode-7.3.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.1.sdk; its version (9.1) is below required minimum (9.3) for the iphonesimulator platform.
2016-07-28 15:34:43.400 instruments[3140:14974] [MT] DVTSDK: Skipped SDK /Applications/Xcode-7.3.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk; its version (9.2) is below required minimum (9.3) for the iphonesimulator platform.
Waiting for device to boot…
Instruments Usage Error: No template (-t) specified
instruments, version 7.3 (60134)
this is indeed an issue with the a template, but simply because we don’t specify one to make it launch quicker. You don’t want to profile your application in any way, you’re simply using xcrun instruments because Instruments is able to launch the GUI iOS simulator reliably (which xcrun simctl isn’t). The Instruments command itself fails, but it launches the iOS simulator anyways. Please add || true at the very end of your command to suppress a non-0 exit code.
this might happen. I’ve seen this before, you might be a special case and this fix wont do the job on your project. I’d love to take a look. Please contact our Support and reference this text, so that I can find your ticket.