Skip to content
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

Timeout: Build took more than 2700 seconds #57

Closed
dagio opened this issue Sep 15, 2016 · 7 comments

Comments

Projects
None yet
2 participants
@dagio
Copy link

commented Sep 15, 2016

Today we are experiencing many build failing because of this timeout. It happens during the Xcode run test step.

It stopped at : Touching MyAppTests.xctest

@dagio

This comment has been minimized.

Copy link
Author

commented Sep 16, 2016

Without xcpretty I managed to get more information :

An error was encountered processing the command (domain=com.apple.CoreSimulator.SimError, code=159):
Unable to erase contents and settings in current state: Booted

I will remove the pre-action that I have that was cleaning the simulator and try again :

# Reset simulator
xcrun simctl erase all
@viktorbenei

This comment has been minimized.

Copy link
Member

commented Sep 16, 2016

Did it work once you removed the pre action?

@dagio

This comment has been minimized.

Copy link
Author

commented Sep 20, 2016

Yes it does

@dagio dagio closed this Sep 20, 2016

@viktorbenei

This comment has been minimized.

Copy link
Member

commented Sep 20, 2016

Wow, so if you do a xcrun simctl erase all it can cause Xcode to hang?? That's one more thing to add to our https://bitrise-io.github.io/devcenter/ios/known-xcode-issues/ list ...

@viktorbenei

This comment has been minimized.

Copy link
Member

commented Sep 20, 2016

Thanks for reporting and for the infos/details! ;)

@dagio

This comment has been minimized.

Copy link
Author

commented Sep 20, 2016

My guess is the test pre action is happening after xcode already start the simulator and do some stuffs. Trying to reset the simulator settings here does not seems to be a good idea because it will mess things up.

@viktorbenei

This comment has been minimized.

Copy link
Member

commented Sep 20, 2016

I agree, but this still shouldn't cause it to hang ;)
Kinda makes sense, but it should print an error instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.