-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins 1.616, Xcode 6.2, Mac OS 10.9 & 10.10
After upgrading our core system to 1.608 (through 1.606) from 1.601, our unit tests have started to hang. They compile fine, but hang when trying to start the simulator.
This was working fine in 1.601.
When running the command in terminal on the local machine, the tests run fine, but run from the JNLP service it hangs. Jenkins seems unable to start the simulator.
The command we have been using is:
/usr/bin/xcodebuild -scheme <SCHEME> -sdk iphonesimulator8.2 -workspace /Users/Shared/Jenkins/Home/workspace/iOS.xcworkspace -configuration Debug build test -destination "platform=iOS Simulator,name=iPhone 5,OS=8.2"
We subsequently upgraded the Xcode plugin from 1.4.5 -> 1.4.8 -> 1.4.5 -> 1.4.8 and found no change. Also, we re-downloaded the JNLP agent and removed/re-installed a build node to try and isolate that too.
[Edit] Added in more specific version information
- is related to
-
-
- Open
-
[JENKINS-27854] iOS Unit Tests hang after Jenkins Update
to 1.608 (through 1.606)
Still not sure what that means, sorry.
It would help if you could narrow down to the specific Jenkins version this issue appeared in. Note that downgrading to before 1.607 will lose slave config information as noted in the changelog.
Oliver Furneaux
added a comment - Yes, we are aware that there could be issues downgrading.
We upgraded from 1.601 where this was working.
We then upgraded to 1.606 as per the security notification, and subsequently upgraded to 1.608 to make sure we were using the latest version of the server.
Does that make more sense?
Oliver Furneaux
added a comment - Yes, we are aware that there could be issues downgrading.
We upgraded from 1.601 where this was working.
We then upgraded to 1.606 as per the security notification, and subsequently upgraded to 1.608 to make sure we were using the latest version of the server.
Does that make more sense? 
Konstantin Tchernov
added a comment - This issue is still present with Jenkins 1.616.
It's a fairly critical issue and we are investigating alternatives to Jenkins as a result.
Any chance of this being fixed?
Konstantin Tchernov
added a comment - This issue is still present with Jenkins 1.616.
It's a fairly critical issue and we are investigating alternatives to Jenkins as a result.
Any chance of this being fixed? 
Ben Kennedy
added a comment - This has been a serious problem for us too; for months we have not been able to run our UTs via Jenkins. Apple seems to blame Jenkins and seems not interested in this scenario. We are looking at moving away from Jenkins for iOS builds.
Ben Kennedy
added a comment - This has been a serious problem for us too; for months we have not been able to run our UTs via Jenkins. Apple seems to blame Jenkins and seems not interested in this scenario. We are looking at moving away from Jenkins for iOS builds. 
lacostej
added a comment - This is a most probably a bug in Xcode 6.2. See http://stackoverflow.com/questions/25380365/timeout-when-running-xcodebuild-tests-under-xcode-6-via-ssh
Can be worked around by "converting your Jenkins configuration from being a LaunchDaemon to being a LaunchAgent"
lacostej
added a comment - This is a most probably a bug in Xcode 6.2. See http://stackoverflow.com/questions/25380365/timeout-when-running-xcodebuild-tests-under-xcode-6-via-ssh
Can be worked around by "converting your Jenkins configuration from being a LaunchDaemon to being a LaunchAgent" Oliver Furneaux
added a comment - We still haven't resolved this in Xcode 7. The linked SO answer requires creating a GUI session. It appears that when using Xcode Server to make builds/run unit tests, there is no requirement for a logged in user. Converting from LaunchDaemon to LaunchAgent is only going solve some of the problems. It also appears the Xcode Server users are running as LaunchDaemons also.
Is there a way for the jenkins user to have similar properties to the build agent that Xcode Server uses? Surely then the node shouldn't need to have created a login session.
Oliver Furneaux
added a comment - We still haven't resolved this in Xcode 7. The linked SO answer requires creating a GUI session. It appears that when using Xcode Server to make builds/run unit tests, there is no requirement for a logged in user. Converting from LaunchDaemon to LaunchAgent is only going solve some of the problems. It also appears the Xcode Server users are running as LaunchDaemons also.
Is there a way for the jenkins user to have similar properties to the build agent that Xcode Server uses? Surely then the node shouldn't need to have created a login session. 
Dima Vartanian
added a comment - I am having this issue as well and I believe there is another issue for this item:
https://issues.jenkins-ci.org/browse/JENKINS-32008
Dima Vartanian
added a comment - I am having this issue as well and I believe there is another issue for this item:
https://issues.jenkins-ci.org/browse/JENKINS-32008 
Was Jenkins core the only component that has been updated? No OS X, Xcode, Jenkins plugin updates?
Please specifically mention the core version this still worked with.