-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't Load Stylesheet twitter/bootstrap/bootstrap.less - Caching problem? #560
Comments
|
Yeah I agree you don't need both. Doing either one still fails. Thanks, I'll try with verbose and report back |
The solution to this problem of not being able to load LESS stylesheets Strangely enough there's no need to run this command if just running rspec, as it will check the asset pipeline if it can't find files in public. But it IS necessary when using parallel specs. Any idea why this is the case? |
might be that it runs it already in one of the forks and the others decide
to not run it ... try running with --verbose and copy-paste one of these
commands to see if they fail individually
…On Tue, Apr 4, 2017 at 4:13 PM, Seyon Vasantharajan < ***@***.***> wrote:
The solution to this problem of not being able to load LESS stylesheets
$RAILS_ENV=test bundle exec rake assets:precompile
Strangely enough there's no need to run this command if just running
rspec, as it will check the asset pipeline if it can't find files in
public. But it IS necessary when using parallel specs.
Any idea why this is the case?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#560 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAsZ4fX2EVUn5jrNQj_H0LwdYoBm29aks5rss6bgaJpZM4MXEVf>
.
|
I'm having a problem with loading a stylesheet when using parallel_tests.
I get
Less::Error at /login 'twitter/bootstrap/bootstrap.less' wasn't found
Specifically, there's a problem with the line
@import "twitter/bootstrap/bootstrap"
present in my bootstrap_and_overrides.css file.There's no problem in either my development server or when I simply run tests without parallel_tests. Not entirely sure what the problem could be.
Adding the following line to test.rb( to make sure that each process accesses its own cache), doesn't seem to help
config.cache_store = :file_store, Rails.root.join("tmp","cache","paralleltests_#{Process.pid}_#{ENV['TEST_ENV_NUMBER']}")
The text was updated successfully, but these errors were encountered: