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

JitPack build fails with "Git clone took longer than 180 s" #2182

Closed
hypest opened this issue Apr 24, 2020 · 2 comments · Fixed by #2183
Closed

JitPack build fails with "Git clone took longer than 180 s" #2182

hypest opened this issue Apr 24, 2020 · 2 comments · Fixed by #2183
Labels
[Type] Bug Something isn't working

Comments

@hypest
Copy link
Contributor

hypest commented Apr 24, 2020

It has been reported (in Slack) a few times already that the JitPack build randomly fails with the following error message (in JitPack's log):

Git error. Retrying.
Git error. Git clone took longer than 180 s

To Reproduce
No steps to reproduce, but it looks like it is too frequent at this point. An example is this WPAndroid PR on which we've failed to make the JitPack build dependency succeed.

@hypest
Copy link
Contributor Author

hypest commented Apr 27, 2020

Looks like the issue is still happening, this time on 30d5f0a, part of the 1.27.0 release cut.

@mchowning
Copy link
Contributor

Closing this since we no longer rely on Jitpack to build the entire gutenberg-mobile library. We do still use it to build some of our React Native dependencies, but those are substantially smaller and have not encountered this "Git clone took longer than 180 s" error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants