https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
Dan Duvall dduv...@wikimedia.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
Bryan Davis bda...@wikimedia.org changed:
What|Removed |Added
See Also|
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #16 from Bryan Davis bda...@wikimedia.org ---
Can we do `apt-get install ruby-ffi` instead of compiling ffi with bunder?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
Bryan Davis bda...@wikimedia.org changed:
What|Removed |Added
Priority|Unprioritized |Normal
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #17 from Dan Duvall dduv...@wikimedia.org ---
The ruby-ffi package is for Ruby 1.9. Perhaps we should try switching back to a
shared directory for bundler gems. That would at least mitigate the failures by
only performing ffi
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #18 from Dan Duvall dduv...@wikimedia.org ---
After profiling the `bundle install` process, I'm seeing around 128M as the
peark memory usage. That seems like a reasonable amount of free memory to
expect on the VM considering some of
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
Bryan Davis bda...@wikimedia.org changed:
What|Removed |Added
Status|REOPENED|UNCONFIRMED
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #10 from Željko Filipin zfili...@wikimedia.org ---
Created attachment 13383
-- https://bugzilla.wikimedia.org/attachment.cgi?id=13383action=edit
vagrant provision
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #9 from Željko Filipin zfili...@wikimedia.org ---
I have the same problem. I will attach output of vagrant enable-role
browsertests and VBoxManage showvminfo.
How do I increase VM memory size? (Looks like it is 768MB now.)
In
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #11 from Željko Filipin zfili...@wikimedia.org ---
Created attachment 13384
-- https://bugzilla.wikimedia.org/attachment.cgi?id=13384action=edit
VBoxManage showvminfo
--
You are receiving this mail because:
You are on the CC
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #12 from Željko Filipin zfili...@wikimedia.org ---
I have tried this.
#1 $ vagrant halt
#2 changed
vb.customize ['modifyvm', :id, '--memory', '768']
in Vagrantfile to
vb.customize ['modifyvm', :id, '--memory', '1024']
#3 $
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #13 from Željko Filipin zfili...@wikimedia.org ---
Found it. Mediawiki-Vagrant[1] says to edit Vagrantfile-extra.rb. Now VM memory
size is 1024.
$ vagrant halt
edit Vagrantfile-extra.rb
$ vagrant up
$ VBoxManage showvminfo ...
...
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #14 from Željko Filipin zfili...@wikimedia.org ---
I managed to get tests running after increasing memory size to 1024. Is it
possible to increase memory size just when gems are installing, and then
decrease it back to 512?
--
You
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
sp...@wikimedia.org changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #6 from sp...@wikimedia.org ---
Created attachment 13289
-- https://bugzilla.wikimedia.org/attachment.cgi?id=13289action=edit
output of `vboxmanage showvminfo ...` before I increased VM memory
--
You are receiving this mail
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #7 from Ori Livneh o...@wikimedia.org ---
(In reply to comment #5)
I increased the VM to 1024, `vagrant halt` `vagrant up`!
And -- did it work? I guess it did, because you later speak of successful and
unsuccessful runs.
I don't
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #8 from sp...@wikimedia.org ---
(In reply to comment #5)
I increased the VM to 1024, `vagrant halt` `vagrant up`!
... that should have continued and the vagrant provision complete
successfully, and I can run tests! Yay, thanks for
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
Ori Livneh o...@wikimedia.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
Andre Klapper aklap...@wikimedia.org changed:
What|Removed |Added
Component|MediaWiki-Vagrant |General
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
--- Comment #2 from Ori Livneh o...@wikimedia.org ---
I ran into this problem before. If I recall correctly, it's an out-of-memory
error that bundler is unhelpfully catching and re-throwing as an uninformative
generic exception. The memory
https://bugzilla.wikimedia.org/show_bug.cgi?id=53864
Chris McMahon cmcma...@wikimedia.org changed:
What|Removed |Added
CC|
21 matches
Mail list logo
