Did something change with the emma tasks to make it not include the source
in the reports any more? All I get is class level coverage statistics
without the actual source files to see what lines were covered. I thought I
remembered running these before and getting the source coverage. I'm
assumi
Lots of spec failures for Time
--
Key: JRUBY-1807
URL: http://jira.codehaus.org/browse/JRUBY-1807
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1.x
String#inspect works incorrectly when KCODE is set
--
Key: JRUBY-1806
URL: http://jira.codehaus.org/browse/JRUBY-1806
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Add feature requests for new Ruby 1.9 features
--
Key: JRUBY-1805
URL: http://jira.codehaus.org/browse/JRUBY-1805
Project: JRuby
Issue Type: New Feature
Reporter: Charles Oliver Nutter
Support Ruby 1.9 GIL, for cases where exact thread behavior compatibility is
important
--
Key: JRUBY-1804
URL: http://jira.codehaus.org/browse/JRUBY-1804
Project: JRu
Support Ruby 1.9 M17N strings
-
Key: JRUBY-1803
URL: http://jira.codehaus.org/browse/JRUBY-1803
Project: JRuby
Issue Type: New Feature
Reporter: Charles Oliver Nutter
Assignee: Thomas E Ene
Support Ruby 1.9 encoding pragmas for parsed files
--
Key: JRUBY-1802
URL: http://jira.codehaus.org/browse/JRUBY-1802
Project: JRuby
Issue Type: New Feature
Reporter: Charles Oliver
Support Ruby 1.9 stabby lambda syntax
-
Key: JRUBY-1801
URL: http://jira.codehaus.org/browse/JRUBY-1801
Project: JRuby
Issue Type: New Feature
Reporter: Charles Oliver Nutter
Assign
Ruby 1.9 Fiber support should leverage the same thread pool as pooled JRuby
threading
-
Key: JRUBY-1800
URL: http://jira.codehaus.org/browse/JRUBY-1800
Project: JRuby
Thread pool should have configurable min/max
Key: JRUBY-1799
URL: http://jira.codehaus.org/browse/JRUBY-1799
Project: JRuby
Issue Type: Bug
Reporter: Charles Oliver Nutter
JRuby JIT should have an upper limit on how many methods can be compiled, to
avoid eating too much permgen
--
Key: JRUBY-1798
URL: http://jira.codehaus.org/bro
Bill Dortch wrote:
Yup, it was the new ObjectProxyCache I committed this morning. Fixed in
r5371. From my comments:
Thanks for digging in and finding the problem. It looks like I'm running
clean now.
"Fixed PermGen issue in build caused by daemon "vulture" thread in new
ObjectProxyCache.
String#% handles null bytes differently than the latest MRI
---
Key: JRUBY-1797
URL: http://jira.codehaus.org/browse/JRUBY-1797
Project: JRuby
Issue Type: Bug
Components: Core
String#each_byte behaves differently than MRI in some cases
---
Key: JRUBY-1796
URL: http://jira.codehaus.org/browse/JRUBY-1796
Project: JRuby
Issue Type: Bug
Components: Core
String#index works incorrectly with FixNum parameters
-
Key: JRUBY-1795
URL: http://jira.codehaus.org/browse/JRUBY-1795
Project: JRuby
Issue Type: Bug
Components: Core Classes/Mod
String#initialize should be private
---
Key: JRUBY-1794
URL: http://jira.codehaus.org/browse/JRUBY-1794
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1.x
String#insert incorrectly handles tainted argument
--
Key: JRUBY-1793
URL: http://jira.codehaus.org/browse/JRUBY-1793
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Yup, it was the new ObjectProxyCache I committed this morning. Fixed in
r5371. From my comments:
"Fixed PermGen issue in build caused by daemon "vulture" thread in new
ObjectProxyCache. OPC was not being finalized due to this thread (which
must have prevented the entire runtime from being fina
18 matches
Mail list logo