Bug ID: 63054
           Summary: labs-vagrant enable browsertests  failure
           Product: MediaWiki-Vagrant
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: Unprioritized
         Component: General
       Web browser: ---
   Mobile Platform: ---

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.
notice: /Stage[main]/Browsertests/Exec[install browsertests bundle]/returns:
Results logged to
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

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"
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

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to