Are some tests supposed to fail? about rails-dev-box HOT 23 CLOSED

Thanks @sobrinho, this cleanup you're doing is much needed ❤️ .

from rails-dev-box.

Ideally they should all pass. What's failing?

from rails-dev-box.

Here is one:

And another:

At the end it's reported Errors in actionview, activerecord, railties.

from rails-dev-box.

The second one seems to mean there's not enough RAM. The first one could be a temporary hiccup in the test suite. @rafaelfranca does that one ring a bell?

from rails-dev-box.

Yes, I actually increased my vm RAM to 3GB, with no results.

from rails-dev-box.

And the first one fails consistently for me actually.

from rails-dev-box.

No, sorry. Travis and locally are passing all tests.

from rails-dev-box.

@rafaelfranca mind if I take a look at your Vagrant file?

from rails-dev-box.

I don't use vagrant. Everything runs in my Mac OS X machine. I thought this error were related to linux but travis run on linux, so it maybe something on this setup.

from rails-dev-box.

👍 thanks Rafael, I'll try with Vagrant.

from rails-dev-box.

I have fixed the one in AV. Can reproduce the ones about memory, going to investigate those later.

from rails-dev-box.

Brilliant. Thanks for the good work Xavier.

On Thursday, May 21, 2015, Xavier Noria <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

I have fixed the one in AV. Can reproduce the ones about memory, going to
investigate those later.

—
Reply to this email directly or view it on GitHub
#102 (comment)
.

Mohamed Wael Khobalatte

from rails-dev-box.

@fxn, the changes broke my tests locally. I'm on Mac OS X and have a case-insensitive file system. The helper method in the test suite correctly detects I am on a case-insensitive filesystem, but still raises a TemplateMissing exception.

Reverting the commit got it working again locally. Just thought you might like to know.

I don't have Vagrant at the moment so I can't see what was going on in the original problem, but I could have a dig around later when I have the time.

from rails-dev-box.

@yoongkang interesting! let's see what you find.

from rails-dev-box.

@fxn I saw it too.

PathResolver#find_template_paths deals with case-insensitive file systems. ?
https://github.com/rails/rails/blob/77a7c4bf7d2ed73cbc2554ef9f0514f6191b2658/actionview/lib/action_view/template/resolver.rb#L202

from rails-dev-box.

@why-el I recently ran into the memory issues setting up the dev environment myself. I was able to work around them by upping the vm RAM to 8GB (host has 16GB, so 8GB for the guest isn't too much of an issue). Not sure how much memory is necessary to get around it, but it seems to be somewhere between 3GB and 8GB if that helps.

from rails-dev-box.

Thanks. Did all tests pass after that? That seems to be the issue still.

from rails-dev-box.

Yes, they were all passing after that for me, though I never saw the actionview errors you encountered (using OSX as the host). I'm not sure it will resolve anything for you, but I believe the base box for this (ubuntu/trusty64) has been updated since you first opened this issue. You could try destroying your box and running vagrant box update to get the latest version of ubuntu/trusty64 and then provision the box with the new version and increase RAM (or just update your ram from the VirtualBox GUI).

from rails-dev-box.

Yep I will do that. Hopefully 5-6GB should do it (host is 8GB).

from rails-dev-box.

Hm guyz. Why did I get this mails
On Aug 8, 2015 12:42 AM, "Mohamed Wael Khobalatte" [email protected]
wrote:

Yep I will do that. Hopefully 5-6GB should do it (host is 8GB).

—
Reply to this email directly or view it on GitHub
#102 (comment)
.

from rails-dev-box.

I ran into the problem with first test. Is it fixed, or not?
I use Vagrant box for test running.

from rails-dev-box.

I've encountered with same issue while working with source of Android OS. It's impossible to build the Android from it's source on case-insensitive file systems. But they have a documentation about it here. Even tough ubuntu has case-sensitive file system by default, Vagrant mimics the hosted file system for shared folders. This means if your host OS has case-insensitive file system then your shared folder will be mounted as case-insensitive. But rest of the virtual machine will be case-sensitive. You can test it by creating two files like foo.txt and Foo.txt in your user's home directory. @rafaelfranca I think your OS X has case-sensitive file system so this is why this tests pass as expected on your local machine.

One workaround maybe using a file server like samba. Don't forget to move source of rails from shared folder to another one on your guest OS. Also not that, symlink does not work! Then configure your samba server and have fun with case-sensitive file system.

But I think instead of a workarounds these tests shouldn't fail on case-insensitive file systems. There was a commit to fix the problem made by @fxn but it's reverted by @matthewd and I couldn't find the reason behind of this revert.

from rails-dev-box.

@fxn I think this can be closed since the issue was detected and the memory is configurable now.

from rails-dev-box.