heroku-buildpack-jemalloc icon indicating copy to clipboard operation
heroku-buildpack-jemalloc copied to clipboard

No heroku-16 build

Open csuhta opened this issue 7 years ago • 4 comments

I have:

$  heroku buildpacks
1. https://github.com/heroku/heroku-buildpack-apt
2. https://github.com/mojodna/heroku-buildpack-jemalloc.git#v3.6.0
3. heroku/ruby

When I deploy, the build phase crashes:

[...]
remote: -----> jemalloc app detected
remote: -----> Vendoring binaries
remote:        Fetching https://s3.amazonaws.com/mojodna-heroku/heroku-16/jemalloc-3.6.0-1.tar.gz
remote: 
remote: gzip: stdin: not in gzip format
remote: tar: Child returned status 1
remote: tar: Error is not recoverable: exiting now
remote:  !     Push rejected, failed to compile jemalloc app.
remote: 
remote:  !     Push failed
[...]

This file doesn't exist: https://s3.amazonaws.com/mojodna-heroku/heroku-16/jemalloc-3.6.0-1.tar.gz

Everything is fine if I don't pin to v3.6.0.

Is there a reason 3.6.0 is still shown as a fallback option? Is it still supported?

csuhta avatar Dec 01 '17 20:12 csuhta

We need to create a heroku-16 build, we haven't done that yet.

nateberkopec avatar Dec 04 '17 16:12 nateberkopec

I have the same exact problem. I read that jemalloc 3.6 works better with Ruby, I'm using Ruby 2.3.1.

egimenos avatar May 04 '18 09:05 egimenos

I encountered this issue today. Are there any plans for building 3.6 for heroku 16? Or should I just be using the latest version instead? I have heard of instabilities with 4.0, and unknown performance with 5.0

timobleeker avatar Jun 19 '18 15:06 timobleeker

See #18.

nateberkopec avatar Jun 21 '18 13:06 nateberkopec