[#90399] [Ruby trunk Feature#14813] [PATCH] gc.c: make gc_enter+gc_exit pairs dtrace probes, too — ko1@...
Issue #14813 has been updated by ko1 (Koichi Sasada).
3 messages
2018/12/10
[#90417] [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD — naruse@...
Issue #15398 has been reported by naruse (Yui NARUSE).
4 messages
2018/12/11
[#90423] Re: [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD
— Eric Wong <normalperson@...>
2018/12/11
[email protected] wrote:
[#90519] Spoofing warnings for mail from bugs.ruby-lang.org — Charles Oliver Nutter <headius@...>
I'm getting a spoofing warning for emails sent from bugs.ruby-lang.org when
4 messages
2018/12/13
[#90522] Re: Spoofing warnings for mail from bugs.ruby-lang.org
— Eric Wong <normalperson@...>
2018/12/13
Charles Oliver Nutter <[email protected]> wrote:
[#90533] [Ruby trunk Feature#15413] unmarkable C stack (3rd stack) — normalperson@...
Issue #15413 has been reported by normalperson (Eric Wong).
3 messages
2018/12/14
[#90581] [Ruby trunk Bug#15424] Ruby 2.6.0rc1 & 2.6.0rc2 mutex exception — mat999@...
Issue #15424 has been reported by splitice (Mathew Heard).
3 messages
2018/12/17
[#90595] [Ruby trunk Bug#15430] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been reported by hsbt (Hiroshi SHIBATA).
3 messages
2018/12/18
[#90614] [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been updated by hsbt (Hiroshi SHIBATA).
4 messages
2018/12/19
[#90630] Re: [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI
— Eric Wong <normalperson@...>
2018/12/20
> It still exists. https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos7/ruby-trunk/log/20181218T230003Z.fail.html.gz
[#90820] Re: [ruby-cvs:73697] k0kubun:r66593 (trunk): accept_nonblock_spec.rb: skip spurious failure — Eric Wong <normalperson@...>
[email protected] wrote:
3 messages
2018/12/30
[ruby-core:90761] [Ruby trunk Misc#15474][Rejected] Running Rails with jit
From:
takashikkbn@...
Date:
2018-12-28 02:42:00 UTC
List:
ruby-core #90761
Issue #15474 has been updated by k0kubun (Takashi Kokubun). Status changed from Open to Rejected RUBYOPT is answered by shevegen. Thanks. It was also explained in release notes. And you can use "ruby --jit bin/rails s" as well. Why do we want to have more ways to specify that? > which should only be respected by ruby >= 2.6.0 I'm not a fan of ignoring no-op config, rather I like asserting the config and making it fail. What if we typo the environment variable name? Even $RUBYOPT should be the last resort, as you typo-ed it to $RUBY_OPTS too. ---------------------------------------- Misc #15474: Running Rails with jit https://bugs.ruby-lang.org/issues/15474#change-75934 * Author: foonlyboy (Eike Dierks) * Status: Rejected * Priority: Normal * Assignee: ---------------------------------------- I have installed ruby-2.6.0 I want to try to run my rails app with the jit. How can this be done? I should try env RUBY_OPTS='--jit' Is this the way the go? The jit ist experimental, but promising, so we need to try it wherever we can. there needs to be a clear documentation, how to enable or disable jit I'd like to enable jit by default, when running 2.6.0 running 2.5.3 with --jit gives: /opt/local/bin/ruby --jit -e 'puts "hello world"' /opt/local/bin/ruby: invalid option --jit (-h will show valid options) (RuntimeError) I'd like to suggest a new env: RUBY_JIT which should only be respected by ruby >= 2.6.0 ~eike -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>