-
Notifications
You must be signed in to change notification settings - Fork 2
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
ncs_mdes does not work on JRuby #5
Comments
Tests continue to fail with JRuby 1.6.7 and Nokogiri 1.5.2. |
Same tests fail with JRuby 1.7.1 and Nokogiri 1.5.5. |
According to sparklemotion/nokogiri#712 the behavior that Nokogiri-Java is exhibiting here is the desired behavior while the behavior of Nokogiri-C < 1.5.5 that the library is uses is a bug. The bug is fixed in Nokogiri 1.5.6; making 1.5.6 the minimum requirement for this library and adapting to that change so that the tests pass will restore JRuby (and now C-Ruby) compatibility. |
Correction: adapting to Nokogiri 1.5.6 fixes 12 out of the 13 JRuby failures. There is still one behavior difference. On JRuby the following test fails:
|
sparklemotion/nokogiri#818 covers the last of these behavior differences. |
This is fixed now, but there's still quite a performance gap between MRI and JRuby, at least for the spec suite. On my machine the spec suite runs in 113s on 1.9.3-p327 vs. 2103s on JRuby 1.7.3 (on Java HotSpot(TM) 64-Bit Server VM 1.6.0_29-b11-402-11E2068 [darwin-x86_64]) — it's more than 18x faster on MRI. |
Several specs fail under JRuby 1.6.4. All of them appear to be related to extracting namespaced attribute values, so I'm guessing it's an incompatibility with Nokogiri. Determine who's at fault and fix it.
When it is working, enable JRuby in the CI build.
The text was updated successfully, but these errors were encountered: