This issue is still persisting, and
Rebuild without cache is not a permanent fix–even after the cache has been cleared and rebuilt, the issue will rear its ugly head within a few days (or hours, depending on how frequently new builds are kicked off).
If any CircleCI Staff are actually reading this forum, it’d be nice to at least get an acknowledgement of the issue.
Here’s the full stack trace I encountered this time around (the native extension that fails to compile is non-deterministic).
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
/opt/circleci/ruby/ruby-2.3.1/bin/ruby -r ./siteconf20170418-15913-1p4u4fv.rb
Ignoring binding_of_caller-0.7.2 because its extensions are not built. Try: gem
pristine binding_of_caller --version 0.7.2
Ignoring byebug-5.0.0 because its extensions are not built. Try: gem pristine
byebug --version 5.0.0
Ignoring nokogiri-18.104.22.168 because its extensions are not built. Try: gem
pristine nokogiri --version 22.214.171.124
`missing_extensions?': undefined method `missing_extensions?' for nil:NilClass
`block in find_by_path'
`rescue in require'
from <internal:gem_prelude>:6:in `<internal:gem_prelude>'
extconf failed, exit code 1
Gem files will remain installed in
Results logged to
An error occurred while installing stackprof (0.2.10), and Bundler
Make sure that `gem install stackprof -v '0.2.10'` succeeds before bundling.
bundle check --path=vendor/bundle || bundle install --path=vendor/bundle --jobs=4 --retry=3 returned exit code 5
Action failed: bundle install