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

[B2G] Sometime reop fetch failed, and need to re-fetch manually #7

Open
snowmantw opened this issue Feb 7, 2014 · 4 comments
Open

Comments

@snowmantw
Copy link

This is a bug need to be solved, if we want to automate the building process.

@snowmantw
Copy link
Author

These two errors:

error: Exited sync due to fetch errors
Repo sync failed

cause the box can't build anything, even after 5+ retries.

@gasolin
Copy link
Owner

gasolin commented Feb 7, 2014

http://stackoverflow.com/questions/16085722/when-running-repo-sync-error-exited-sync-due-to-fetch-errors

Invoking repo sync -f -j10 did the trick.

As it seems -f or --force-broken flag allows it to recover from network error and more important recover on broken/missing objects.

Maybe we can provide a set of script to run this command

@snowmantw
Copy link
Author

I gave up it temporarily and launch a GCE instance to test, and found that the network really affected the building. In foxbox it just failed again and again, and GCE instance would success. This may be a issue we must solve, because I failed at a standard and fast enough network.

@gasolin
Copy link
Owner

gasolin commented Feb 10, 2014

You could check 14644ad if it fix this issue

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

No branches or pull requests

2 participants