-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assertion failure in ROCKRemoteProxy (Xcode Build Task, Hosted Agent, MacOS) #8840
Comments
I did get this problem using fastlane and travis ci |
I'm also seeing this in ~1/10 builds using Fastlane and TeamCity with Xcode 10 |
I am getting the same error on Azure Devops Pipelines, but while running
The tests itself work just fine, but the command still returns an error:
|
same here:
|
We started seeing this randomly on some travis builds after switching from Xcode 10 to Xcode 10.1 |
Also seeing this consistently on TravisCI only on Xcode 10.1 |
I have researched this a lot and have not gotten anywhere so far. This is what I found out so far:
|
This also happens in builds with Xcode 9.4.1. |
Same problem here. Xcode 10.1 |
We're also seeing this error on the hosted mac pool at the end of our unit tests. I can't give a guess at the frequency, but 1 in 10 seems reasonable. |
Same happens running Fastlane with Bitrise |
We're seeing the issue running a plain |
This is clearly not specific to Azure Pipelines, so closing this issue. The thread has a lot of useful details, thanks to all for sharing. We are not changing anything in Azure Pipelines or the Hosted macOS VMs yet but will be reviewing any workarounds we can provide to mitigate this issue. |
FYI, we are experiencing the same problem in my team and the only solution we found was to have some logic that would retry the command when this particular problem is detected. |
When running a Xcode build on Hosted Agent (macOS) I get this error on 1 in a 10 builds. I do not know where it originates (not in our code). The error output is after the Xcode build is done (succeeded).
Not sure if this is the right place to report this.
Anyone know anything about this and have seen it?
The text was updated successfully, but these errors were encountered: