Project

Profile

Help

Issue #3376

New builder dependency fails to build with OSCI environment

Added by bmbouter almost 3 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

I recently upgraded the ruby gem dependencies and I broke the OSCI builder. The build log says bundler is older than in my gem file and that it's missing libffi-devel.

last_build_date: 2018-02-16 00:03:02 (UTC)
last_build_commit: 7905889525c1ee09a41985abcf1f7a82a0870a69
submodule_commits: {}

No local changes to save

Already up-to-date.

Warning: the running version of Bundler (1.13.7) is older than the version that created the lockfile (1.16.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
Fetching gem metadata from https://rubygems.org/..........
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Using concurrent-ruby 1.0.5
Using minitest 5.11.3
Using thread_safe 0.3.6
Using public_suffix 2.0.5
Using coffee-script-source 1.11.1
Using execjs 2.7.0
Using colorator 1.1.0
Installing ffi 1.9.21 with native extensions
Using multipart-post 2.0.0
Using forwardable-extended 2.6.0
Using gemoji 3.0.0
Using net-dns 0.8.0
Using rb-fsevent 0.10.2
Using kramdown 1.16.2
Using liquid 4.0.0
Using mercenary 0.3.6
Using rouge 2.2.1
Using safe_yaml 1.0.4
Using mini_portile2 2.3.0
Using jekyll-paginate 1.1.0
Using rubyzip 1.2.1
Using jekyll-swiss 0.4.0
Using unicode-display_width 1.3.0
Using bundler 1.13.7
Using i18n 0.9.5
Using tzinfo 1.2.5
Using addressable 2.5.2
Using coffee-script 2.4.1
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    current directory: /srv/builder/.gem/ruby/2.4.0/gems/ffi-1.9.21/ext/ffi_c
/usr/bin/ruby -r ./siteconf20180215-1821-111t5k2.rb extconf.rb
checking for ffi.h... no
checking for ffi.h in /usr/local/include,/usr/include/ffi... no
checking for shlwapi.h... no
checking for rb_thread_blocking_region()... no
checking for rb_thread_call_with_gvl()... yes
checking for rb_thread_call_without_gvl()... yes
creating extconf.h
creating Makefile

current directory: /srv/builder/.gem/ruby/2.4.0/gems/ffi-1.9.21/ext/ffi_c
make "DESTDIR=" clean
rm -f 
rm -f ffi_c.so  *.o  *.bak mkmf.log .*.time

current directory: /srv/builder/.gem/ruby/2.4.0/gems/ffi-1.9.21/ext/ffi_c
make "DESTDIR="
Running autoreconf for libffi
/srv/builder/.gem/ruby/2.4.0/gems/ffi-1.9.21/ext/ffi_c/libffi/autogen.sh: line
2: exec: autoreconf: not found
make: *** [libffi.mk:7:
"/srv/builder/.gem/ruby/2.4.0/gems/ffi-1.9.21/ext/ffi_c/libffi-x86_64-linux"/.libs/libffi_convenience.a]
Error 127

make failed, exit code 2

Gem files will remain installed in /srv/builder/.gem/ruby/2.4.0/gems/ffi-1.9.21
for inspection.
Results logged to
/srv/builder/.gem/ruby/2.4.0/extensions/x86_64-linux/2.4.0/ffi-1.9.21/gem_make.out

An error occurred while installing ffi (1.9.21), and Bundler cannot continue.
Make sure that `gem install ffi -v '1.9.21'` succeeds before bundling.

Is it possible someone could add this to the OSCI build environment?

History

#1 Updated by bmbouter almost 3 years ago

  • Status changed from NEW to CLOSED - NOTABUG

I'm not sure what changed, but the most recent website change did build correctly. I'm closing the issue as NOTABUG since I'm not sure what resolved it.

#2 Updated by bmbouter over 2 years ago

  • Status changed from CLOSED - NOTABUG to CLOSED - CURRENTRELEASE

Actually I learned what changed so I'm recapping here. This was fixed by duck and @misc by upgrading the Jekyll builder environment and installing some deps. They are handling ensuring those changes are reflected permanently in the Ansible roles they use for the Jekyll build environment. Those aren't specific to Pulp so I'm not tracking it here.

Since it was broken and then fixed, I'm moving to CLOSED - CURRENT RELEASE.

Thanks so much duck and @misc!

Please register to edit this issue

Also available in: Atom PDF