If you get stuck while working on the bug, leave a comment here and somebody will help you out. I promise.

What needs to be done:

#1 Test if Setup virtual machine[1] section is still up to date (but it is probably not). If it is not up to date, update it.

#2 Depending on the operating systems you have, check if Ruby on Windows/Mac/Linux section is still up to date (but it is probably not). If it is not up to date, update it. You will at least have to update Ruby version to the latest released one.

1: https://www.mediawiki.org/wiki/Browser_testing/setup_instructions#Setup_virtual_machine
2: https://www.mediawiki.org/wiki/Browser_testing/setup_instructions#Setup_your_computer

einyxdotcom wrote:

Hi, my claim has just been accepted for this task, I've been working to test if the 'Setup virtual machine' section works. So far I've discovered that:

VirtualBox 4.3.2 has a error on Windows that messes up with private networks, and vagrant doesn't work with it, therefore it is required to downgrade to VirtualBox 4.2.18

Secondly, I've ran into issues when doing 'vagrent up' that causes this error to occur:

"[default] Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open."

I'm not entirely sure how to fix this error, some quick searches came up with changing a setting in the vm on VirtualBox (Settings > System > Processor > Enable PAE/NX) which didn't work. I've also tried booting into BIOS to check that Virtualization is enabled, it was and therefore this also didn't work. I've also tried running the vm from VirtualBox to no avail.

I'll update here if I manage to solve this and get it running, then I'll move on to testing the Ruby section on Windows 8.1 (this is the only OS I'm running currently) and then I'll update the wiki article.

If you have any ideas on how to solve the issue stated above, it'd be much appreciated, David.

David,

you should send e-mail to QA mailing list[1], maybe somebody there will know what to do.

You should also report a bug in this Bugzilla instance[2]: "Enter a new bug" > "MediaWiki‑Vagrant".

You could also contact Vagrant and/or VirtualBox support and ask if they know what is the problem.

1: https://lists.wikimedia.org/mailman/listinfo/qa
2: https://bugzilla.wikimedia.org/

If you need more information (and you probably do), feel free to ask questions
here, at #wikimedia-qa freenode IRC channel or at QA mailing list:

https://lists.wikimedia.org/mailman/listinfo/qa

jhall wrote:

Completed for this Google Code-in task:

https://www.google-melange.com/gci/task/view/google/gci2013/5888156557639680