I have a project written in Swift with a main target and two test targets: one for unit testing using quick framework and it has 3 KIF tests.
The other target has the XCUITests.
So whenever I run Xcode bot integration with our Xcode CI Server, I get the following error:
Bot Issue for Acceptance Bot (error)
Integration #63 of Acceptance Bot
Open in Xcode: xcbot://iosci/botID/1229919cecfcd510f090e37aed014a23/integrationID/16a3709d3ae008a68a65ff2fe9bb5a7b
Assertion: Test target MyUITests encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)
File: (null):(null)
Introduced 2 integrations ago
Full logs for this integration are attached.
I get this error when I run it into a simulator integration though it runs fine when I connect the CI server with a physical device and run it.
Note: I'm using Xcode 7.3 with Carthage 0.11.
I was facing the same error (although I was using fastlane to run my UI Tests).
The issue was due to the simulator being stuck on a system alert which the UI Tests did not handle. After that all my tests failed and subsequent runs continued to fail as the simulator was not responding.
I logged into the machine and click OK on the disrupting alert and everything was back to normal.
In my case the alert came up since the application was trying to register of APNS and the
"App Name" would like to enable Notifications alert was displayed. Skipping the APNS registration for UI Tests prevented the issue from popping again.
Related
I have been consistently running into this since Xcode 11 and it only happens with a tvOS project. The issue is that I run the code, make some changes, and then run again but the changes aren't incorporated into the build that is run. If I then run it again, they are. This means for each change I have to run the build twice. This even includes added debugger breakpoints. This occurs on an actual Apple TV but was not an issue prior. I do not have this issue at all for any iOS projects. Why are changes only being incorporated every other run?
I am getting a strange error from sidekick cloud build since a few hours ago.
I was building the app successfully, but all of a sudden, it gives me the following error and even reversing the changes does not fix anything. I have even tried with a fully working version of my git repo.
[19-01-28 16:55:27.709] Build step started.
[19-01-28 16:55:37.465] (CLI) Unable to apply changes on device: a754d27bafb8bb273e444b9d6cefd370cd55f4d4. Error is: Build failed..
[19-01-28 16:55:37.469] Error detected during LiveSync on a754d27bafb8bb273e444b9d6cefd370cd55f4d4 for C:\Users\Afshar\Desktop\myapp. Error: Build failed.
I doesn't give me any more details about the issue.
I was wondering if anyone knows how to get more logs in cloud build or if this is a known issue?
Thanks
It happens with me as well for reasons unknown. I couldn't find any root cause, but I did notice one pattern. It usually happens when I am already running the app on an Android Emulator/Device.
When we execute tns run android --bundle, it listens for file changes after the first build and does some webpack incremental build thing afterwards, right?
At the same time, once Sidekick delivers a successful iOS build, it also starts listening for changes to do the webpack incremental builds on iOS.
So while we have these two LISTENERS active and we request for another iOS cloud build, before Sidekick communicates with the cloud, it modifies some files which the android listener detects and results in an incremental android build, which in turn modifies some other files, which the iOS listener detects, resulting in Sidekick trying to do the incremental iOS build but this time its stuck between giving you the incremental update and the new requested cloud build, so it throws you this LiveSync error.
Moral of the story: Try to request cloud builds, when these listeners are inactive.
I finally managed to solve it.
In case anyone else faces this issue, I tried the following command using a hint on this page and it solved the problem.
https://docs.nativescript.org/troubleshooting
tns platform remove ios
and then, I was able to build the project in sidekick.
I have a set of Java GUI tests on Windows that sometimes fail to cleanup a file or a window due to a lock. The next time any test starts I get a "Failed to start build #XXX on agent" message. The build then fails very quickly on that agent, which frees the agent to run another build and this results in a lot of builds failing with the same message on the same agent.
Is there a way to disable the agent when the problem occurs and maybe send a notification?
Rather than disabling the agent, you could try cleaning the files which get locked. Try using Swabra (Build Files Cleaner)
I have coded UI tests running locally just fine, because I can open up IE and point the window at localhost. When I attempt to run these tests on the build server, they fail because the window isn't open yet. How can I get an instance of IE open on the build server as part of these tests, for these tests to run against?
Try giving interactive logon permission to your account underwhich build is running...
So we make use of TeamCity as a CI server (v 7.1.1). And we use MS' own web deployment tool as a means of publishing to our servers (standard ASP.NET fare). However, I've noticed that the batch files that are generated by web deploy seem to play badly with TeamCity.
This is what appears in the build log:
http://dpaste.com/826346/
The script clearly says an error has happened. However, TC seems unable to detect this, as no red lights come on. Is there a (good) way to fix and detect this, so we don't get incorrect build runner status reports? TC is currently setup so that the deployment script is executed by a Command Line runner.
To fix it, change the IIS site AppPool to .net version 4.0 - Your error message says that the app expects 4.0 but web deployment tool is finding 2.0
To detect it, I think you can configure the Build Failure Condition, to fail a build when "an error message is logged by build runner".