9

This issue started today for no apparent reason. When I do git push dev master for my Django project, I sometimes get a hang after the program says "installing dependencies with pip":

Counting objects: 11, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 643 bytes, done.
Total 7 (delta 5), reused 0 (delta 0)

-----> Python app detected
-----> No runtime.txt provided; assuming python-2.7.4.
-----> Using Python runtime (python-2.7.4)
-----> Installing dependencies using Pip (1.3.1)

After 15 minutes of hanging, compilation times out.

Then I run the same command again (without having changed anything), and it works. I suspected it was a problem installing one of the modules in my requirements.txt file, but I made that file empty and the problem still occurs.

My logs just show this:

heroku[slug-compiler]: Slug compilation started

Any ideas how I can troubleshoot this?

RexE
  • 17,085
  • 16
  • 58
  • 81
  • 5
    Looks like a common problem others are having too (including myself). https://status.heroku.com/ isn't much help. I pushed once this morning and it worked, but for the most part, I'm running into this as well. Extending the compile time duration doesn't help. – Corey Farwell Aug 31 '13 at 18:39
  • Few! I thought I was the only one. I had checked Twitter, and that website, but they said everything was normal, it's good to see it's not just me. :) – GangstaGraham Aug 31 '13 at 19:29
  • @RexE , if you have a paid account, do you mind asking customer support what's up, and then posting what they say here? (I have a free account - so I can't contact them) – GangstaGraham Aug 31 '13 at 19:40
  • @GangstaGraham I have a free account too :( – RexE Aug 31 '13 at 20:12
  • same issues here its stuck – SRN Aug 31 '13 at 22:37
  • Same issue. Just commenting so hopefully others don't spend an hour trying to fix it, like I did! I tried creating whole new app from scratch and still the same problem. – Sahand Sep 01 '13 at 00:58

1 Answers1

1

A bit of a far shot, but ... you could try

git fsck --full --strict

to make sure your repository is healthy.

stackunderflow
  • 953
  • 7
  • 17