Skip to content

Instantly share code, notes, and snippets.

@guilhermesilveira

guilhermesilveira/gist:3315116

Created August 10, 2012 15:40
Show Gist options
  • Save guilhermesilveira/3315116 to your computer and use it in GitHub Desktop.
Save guilhermesilveira/3315116 to your computer and use it in GitHub Desktop.
Download ZIP
heroku does not love me anymore
Raw
gistfile1.txt
# updated from https://gist.github.com/3316290
rm -rf xpto
rails _3.2.8_ new xpto -d postgresql --skip-bundle
cd xpto
bundle install
git init
git add .
git commit -m "first commit"
heroku create
git push heroku master
@ideamonk
Copy link

Some of my previously working repos are failing in a similar way. New ones too. There's no indication of the exact step which fails.

-----> Compiled slug size is 9.6MB -----> Launching... ! Heroku push rejected due to an unrecognized error.

heroku logs show these -

2012-08-10T17:46:26+00:00 heroku[slugc]: Slug compilation started 2012-08-10T17:47:44+00:00 heroku[slugc]: Slug compilation failed: unrecognized error

It reports compiled slug size, while on the contrary logs show that slug compilation failed. It hasn't much to do with asset pre-compilation as I tried that too.

In a failed attempt where I left out sqlite by mistake for production in Gemfile, I saw this -

Gem files will remain installed in /tmp/build_34tcr0zxdzhag/vendor/bundle/ruby/1.9.1/gems/sqlite3-1.3.6 for inspection.

So I thought it might help to specify ruby version as 1.9.3 in Gemfile - https://devcenter.heroku.com/articles/ruby-versions

An increase of 10M in slug size but still no results,

-----> Launching...
 !     Heroku push rejected due to an unrecognized error.
 !     We've been notified, see http://support.heroku.com if the problem persists.

To [email protected]:whispering-hamlet-5132.git```

But I wonder why isn't anyone else complaining, is it a 3.2.8 issue ?

@guilhermesilveira
Copy link
Author

I was using 3.2.3 and had the issue so I updated to 3.2.8... not a minor rails update issue. I've opened a ticket at support, lets see...

thanks!

@ideamonk
Copy link

Just tried 3.2.7 too -> fail. I don't think there was a change that I could've missed. Tried from new accounts and new machines too !

@matteomeli
Copy link

I have the same error with 3.2.6, 3.2.7, 3.2.8 with new repos. An old one with 3.2.6 works fine, but cannot create any new one at the moment. I have a ticket open at support too... let's see what happens.

@matteomeli
Copy link

well, tried to push right now and it worked with rails 3.2.6!

@matteomeli
Copy link

update: just created a new repo with rails 3.2.8, no problems at all now.

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