Page MenuHomePhabricator

vagrant git-update error "could not allocate 218103807 bytes for translation cache"
Open, Needs TriagePublic

Description

It also pauses for quite a while before outputting this.

$ vagrant git-update
[..]


==> Updating /vagrant/mediawiki/skins/Vector ...
First, rewinding head to replay your work on top of it...
Fast-forwarded master to 91c84b5eab3faa0297214ef7988b99d4863e8fd5.

From https://gerrit.wikimedia.org/r/p/mediawiki/skins/Vector
   0c4b2c1..91c84b5  master     -> origin/master
 * [new branch]      REL1_27    -> origin/REL1_27
 * [new branch]      wmf/1.27.0-wmf.22 -> origin/wmf/1.27.0-wmf.22
 * [new branch]      wmf/1.27.0-wmf.23 -> origin/wmf/1.27.0-wmf.23
mwv_composer /vagrant/mediawiki
mwv_composer /vagrant/mediawiki/extensions/AbuseFilter
mwv_composer /vagrant/mediawiki/extensions/AntiSpoof
mwv_composer /vagrant/mediawiki/extensions/CheckUser
mwv_composer /vagrant/mediawiki/extensions/Cite
mwv_composer /vagrant/mediawiki/extensions/CodeEditor
mwv_composer /vagrant/mediawiki/extensions/Echo
mwv_composer /vagrant/mediawiki/extensions/EventLogging
==> Updating composer dependencies in /vagrant/mediawiki ...

could not allocate 218103807 bytes for translation cache
mwv_composer /vagrant/mediawiki/extensions/Flow
==> Updating composer dependencies in /vagrant/mediawiki/extensions/AbuseFilter ...

could not allocate 218103807 bytes for translation cache
mwv_composer /vagrant/mediawiki/extensions/ParserFunctions
==> Updating composer dependencies in /vagrant/mediawiki/extensions/AntiSpoof ...

could not allocate 218103807 bytes for translation cache
mwv_composer /vagrant/mediawiki/extensions/PerformanceInspector
==> Updating composer dependencies in /vagrant/mediawiki/extensions/CheckUser ...

could not allocate 218103807 bytes for translation cache
mwv_composer /vagrant/mediawiki/extensions/Renameuser
==> Updating composer dependencies in /vagrant/mediawiki/extensions/Cite ...

could not allocate 218103807 bytes for translation cache
mwv_composer /vagrant/mediawiki/extensions/Scribunto
==> Updating composer dependencies in /vagrant/mediawiki/extensions/CodeEditor ...

could not allocate 218103807 bytes for translation cache
mwv_composer /vagrant/mediawiki/extensions/SpamBlacklist
==> Updating composer dependencies in /vagrant/mediawiki/extensions/Echo ...

could not allocate 218103807 bytes for translation cache
mwv_composer /vagrant/mediawiki/extensions/SyntaxHighlight_GeSHi
==> Updating composer dependencies in /vagrant/mediawiki/extensions/EventLogging ...

could not allocate 218103807 bytes for translation cache
mwv_composer /vagrant/mediawiki/extensions/TemplateData
mwv_composer /vagrant/mediawiki/extensions/Thanks
mwv_composer /vagrant/mediawiki/extensions/TitleBlacklist
mwv_composer /vagrant/mediawiki/extensions/UniversalLanguageSelector
mwv_composer /vagrant/mediawiki/extensions/UserMerge
mwv_composer /vagrant/mediawiki/extensions/VisualEditor

See also:

Event Timeline

Krinkle created this task.May 10 2016, 6:02 PM
Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptMay 10 2016, 6:02 PM
Krinkle updated the task description. (Show Details)May 10 2016, 6:03 PM
bd808 added a subscriber: bd808.May 10 2016, 6:07 PM

I think this is more generally an HHVM problem than a MediaWiki-Vagrant problem, but maybe there is something going on in your VM or our config that trips hhvm up.

I actually encountered this error when simply trying to run hhvmsh on my vagrant install. I messed with the vagrant base memory allocation and the error went away. Unfortunately, reverting the prior configuration didn't make the error return.

That being said, wikimedia-vagrant is currently configured to use 8 cores and only 1536 bytes of memory. Both of which "may" not be a good common config (too many cores, not enough memory).

Personally, I haven't see this for a few months. However, at some point in the last 12 months I did set the following:

.settings.yaml
---
vagrant_ram: 2048
vagrant_cores: 4