Last modified: 2014-09-26 16:24:34 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T65054, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63054 - labs-vagrant enable browsertests failure
labs-vagrant enable browsertests failure
Status: RESOLVED FIXED
Product: MediaWiki-Vagrant
Classification: Unclassified
labs-vagrant (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-25 02:03 UTC by spage
Modified: 2014-09-26 16:24 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description spage 2014-03-25 02:03:39 UTC
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
Comment 1 Bryan Davis 2014-06-05 18:50:12 UTC
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.
Comment 2 Bryan Davis 2014-06-17 15:54:49 UTC
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?
Comment 3 Bryan Davis 2014-08-19 21:43:08 UTC
Needs to be retested.
Comment 4 Bryan Davis 2014-09-26 16:24:34 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links