Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

heroku deploys are taking a loooooooooong time #985

Closed
chadwhitacre opened this issue May 28, 2013 · 10 comments
Closed

heroku deploys are taking a loooooooooong time #985

chadwhitacre opened this issue May 28, 2013 · 10 comments

Comments

@chadwhitacre
Copy link
Contributor

Blocks on "Cleaning up ..."

@chadwhitacre
Copy link
Contributor Author

And then again on "Procfile declares types -> web"

@chadwhitacre
Copy link
Contributor Author

Blech, just timed out. :-(

-----> Discovering process types
       Procfile declares types -> web


 !     command='/usr/bin/mksquashfs /tmp/build_3oichkvrloxcl /tmp/slug_3oichkvrloxcl.img -all-root -noappend' exit_status=0 out='Parallel mksquashfs: Using 4 processors
Creating little endian 3.1 filesystem on /tmp/slug_3oichkvrloxcl.img, block size 131072.
TIOCGWINZ ioctl failed, defaulting to 80 columns
[==============================                                ] 3578/7175  49%' at=timeout elapsed=3.4873716831207275
 !     See https://devcenter.heroku.com/articles/slug-compiler#time-limit

@chadwhitacre
Copy link
Contributor Author

Okay, worked the next time.

Compiled slug size: 40.5MB

So it's not that big.

I should start timing these.

@chadwhitacre
Copy link
Contributor Author

Via Twitter:

Still having trouble? Reach out to me directly. I'm happy to help.

@chadwhitacre
Copy link
Contributor Author

@chadwhitacre
Copy link
Contributor Author

Unsetting BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-python.git#v17

@chadwhitacre
Copy link
Contributor Author

It's detecting it as a node app, which must be why we set BUILDPACK_URL in the first place.

@chadwhitacre
Copy link
Contributor Author

I reset BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-python.git, and now it's blocking at Cleaning up ... again. The app is down.

@chadwhitacre
Copy link
Contributor Author

Did a heroku releases:rollback nnn, per @kennethreitz in IRC. That got us back up, thankfully.

@chadwhitacre
Copy link
Contributor Author

@kennethreitz solved this in #1045. He debugged by cloning the app using heroku fork and ... bashing away at it? What logging did you look at to debug, @kennethreitz?

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

No branches or pull requests

1 participant