Page MenuHomePhabricator

labs-vagrant enable browsertests failure
Closed, ResolvedPublic

Description

I created a labs instance in eqiad with the labs-vagrant role.
After copying over /home/vagrant from pmtpa instance, sudo labs-vagrant provision failed with: various notices and an error:

notice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns: Installing ffi (1.9.3) with native extensions /usr/lib/ruby/1.9.1/rubygems/installer.rb:552:in `rescue in block in build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)
...
notice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns: Results logged to /home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.3/ext/ffi_c/gem_make.out
...
notice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns: You have to install development tools first.
...4 returned 1 instead of one of [0] at /vagrant/puppet/modules/browsertests/manifests/init.pp:85

BTW /vagrant/logs/puppet/ is empty.

But gcc and make are present

/home/vagrant/.gem/ruby/1.9.1/gems/ffi-1.9.3/ext/ffi_c/mkmf.log contains :

package configuration for libffi is not found
"gcc -o conftest -I/usr/include/ruby-1.9.1/x86_64-linux -I/usr/include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -fno-strict-aliasing -g -g -O2 -fPIC conftest.c -L. -L/usr/lib -L. -rdynamic -Wl,-export-dynamic -lruby-1.9.1 -lpthread -lrt -ldl -lcrypt -lm -lc"
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main() {return 0;}
/* end */

I can compile that program if I enter it myself, so I think something went wrong after it.

I reran sudo labs-vagrant provision and this time it completed with no errors, but I still don't have cucumber


Version: unspecified
Severity: normal

Details

Reference
bz63054

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:00 AM
bzimport added a project: Labs-Vagrant.
bzimport set Reference to bz63054.
bzimport added a subscriber: Unknown Object (MLST).

Dan is working on a patch for mw-vagrant in general to make the browsertests role better at https://gerrit.wikimedia.org/r/#/c/137483/. When this is merged or at least stable for testing it would be nice to test the changes in labs-vagrant to see if it fixes these issues.

S, Dan's update to the gem management have been merged. Do you have time to test setting up the browsertest role on a labs instance to see if your issues are fixed now?

Should be fixed by https://gerrit.wikimedia.org/r/#/c/158564/ where Dan switched to using deb packages to install ruby-ffi and other ruby gems.