-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
Add jruby-9000
to testing matrix
#288
Conversation
@softwareanimal could you please pull this branch down and try it out? I can't seem to get CI working with JRuby 9000 (this project uses required keyword arguments, so I assume other versions won't work). |
Unfortunately, Travis explicitly disables C extensions for JRuby: http://docs.travis-ci.com/user/languages/ruby/#JRuby%3A-C-extensions-support-is-disabled This makes installing |
I just ran it with JRuby-9.0.4.0 and it built it but it then fails on the helper:
That's after it built it fine. also:
|
I think that is a new issue stemming from the latest ember-cli and ember-cli-sri. Could you try adding the following to your module.exports = function(defaults) {
var app = new EmberApp(defaults, {
SRI: { enabled: false }
// ...
});
}; |
I did it and got the same error. |
Might be caused by jonathanKingston/broccoli-sri-hash#10? |
@nadavshatz what version of |
|
@nadavshatz EmberCLI 1.13.13 was released today with a fix for that ember-cli-sri bug that we might've been running into. Would you mind updating your CLI and trying this again? |
Closes [#241]. No longer redirects `STDERR` to `STDOUT` via the `STDOUT` file descriptor (as described in the [`Kernel#spawn`][spawn] documentation). Related to [jruby/jruby#3038]. Uses `poltergeist` instead of `capybara-webkit`. Unfortunately, testing for `jruby` support is impossible until [thoughtbot/capybara-webkit#725][#725] is resolved. [#241]: #241 [spawn]: http://ruby-doc.org/core-2.2.3/Kernel.html#method-i-spawn [jruby/jruby#3038]: jruby/jruby#3038 [#725]: thoughtbot/capybara-webkit#725
I'm still getting the same error even with |
@nadavshatz what version of https://github.com/rondale-sc/ember-cli-rails-addon/ are you on? |
@seanpdoyle 0.5.1 |
@nadavshatz which application server are you using? https://github.com/thoughtbot/ember-cli-rails#serving-from-multi-process-servers-in-development If you're using a forking server, how many threads and workers do you have? |
@seanpdoyle I tried. I'm using Puma indeed. It was defaulting to 0-16 threads with a single worker. I ran it manually with 1 thread and a single worker.
Still got the same error: |
@nadavshatz would you be able to distill the problem are to a small sample app that I could clone and debug? |
@nadavshatz here's a Puma config for a working app that consumes EmberCLI-Rails: # https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server#config
workers Integer(ENV["WEB_CONCURRENCY"] || 2)
threads_count = Integer(ENV["MAX_THREADS"] || 5)
threads threads_count, threads_count
preload_app!
rackup DefaultRackup
port ENV["PORT"] || 3000
environment ENV["RACK_ENV"] || "development"
on_worker_boot do
# Worker specific setup for Rails 4.1+
# See: https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server#on-worker-boot
ActiveRecord::Base.establish_connection
end With the following ENV: WEB_CONCURRENCY=1
MAX_THREADS=1 |
I created a clean small project and it worked fine in it. :\ so I'm not sure what is the problem. |
Closes #241.
No longer redirects
STDERR
toSTDOUT
via theSTDOUT
filedescriptor (as described in the
Kernel#spawn
documentation).Related to jruby/jruby#3038.
Uses
poltergeist
instead ofcapybara-webkit
.Unfortunately, testing for
jruby
support is impossible untilthoughtbot/capybara-webkit#725 is resolved.