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

GIT Warning #136

Closed
Brett-Best opened this issue Sep 27, 2015 · 11 comments
Closed

GIT Warning #136

Brett-Best opened this issue Sep 27, 2015 · 11 comments

Comments

@Brett-Best
Copy link
Contributor

An error occurred updating existing checkout. Falling back to a clean checkout.
My normal bots produce the above warning after Buildasaur runs a PR bot.

@czechboy0
Copy link
Member

If you push to the branch of this PR again, and another integration happens, does that also have this warning? I've seen this on the 1st integration only, so I'm wondering if it goes away with more integrations or not.

@czechboy0
Copy link
Member

Can you reliably reproduce this on every new PR Bot created by Buildasaur?

@Brett-Best
Copy link
Contributor Author

@czechboy0 once buildasaur does a PR bot the first time normal bots run it happens.

@Brett-Best
Copy link
Contributor Author

Something to do with my creation of the xccheckout file I wonder.

@czechboy0
Copy link
Member

Right, maybe it's that, yeah. Are you sure you modified all the values properly? Maybe going through it again to see might be worth it. Because I'm not seeing this error at all on my Mac.

@Brett-Best
Copy link
Contributor Author

@czechboy0 yes I replaced all of the values correctly.

@czechboy0
Copy link
Member

Hey @Brett-Best, is this still happening?

@Brett-Best
Copy link
Contributor Author

@czechboy0 yes it is.

@czechboy0
Copy link
Member

@Brett-Best Can you please read through the conversation in #140, which got resolved. Maybe creating the checkout file by hand won't be the best way to go. In #140, there are two possible fixes mentioned:

  • upgrade Buildasaur to 0.5.0, which now also parses xcscmblueprint files
  • if that doesn't help, if possible, open your project in Xcode 6.4, which should create the old checkout file for you

Before you do either one, I suggest you remove your existing checkout file (the one created by hand), which might turn out to be corrupt - I think that's causing this warning.

Please let me know what helped, thanks! 👍

@czechboy0
Copy link
Member

Hey @Brett-Best, can you please try the above? Otherwise there's nothing I can do about it at the moment.

@Brett-Best
Copy link
Contributor Author

@czechboy0 it seems it may be resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants