Skip to content
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

coderay 1.0.0 fails tests on jruby #4

Closed
graaff opened this issue Sep 21, 2011 · 8 comments
Closed

coderay 1.0.0 fails tests on jruby #4

graaff opened this issue Sep 21, 2011 · 8 comments
Labels

Comments

@graaff
Copy link

graaff commented Sep 21, 2011

Trying to run coderay's tests on JRuby (jruby 1.5.6 (ruby 1.8.7 patchlevel 249) (2011-06-08 6586) (OpenJDK 64-Bit Server VM 1.6.0_22) [amd64-java]) gives me the following test failures:

/usr/bin/jruby ./test/unit/suite.rb
Running CodeRay unit tests: comment_filter, count, debug, duo, file_type, filter, json_encoder, lines_of_code, null, plugin, statistic, text, token_kind_filter, tokens, word_list
Loaded suite ./test/unit/suite
Started
..........Block supersedes default value argument; use either.
F.......................F..................
Finished in 0.577 seconds.

  1) Failure:
test_block_supersedes_default_warning(FileTypeTests) [./test/unit/file_type.rb:31]:
<"Block supersedes default value argument; use either.\n"> expected but was
<"">.

  2) Failure:
test_plugin_not_found(PluginScannerTest) [./test/unit/plugin.rb:58]:
<CodeRay::PluginHost::PluginNotFound> exception expected but none was thrown.

53 tests, 158 assertions, 2 failures, 0 errors
@korny
Copy link
Member

korny commented Sep 21, 2011

I tested on 1.6.4. Will investigate.

@korny
Copy link
Member

korny commented Sep 21, 2011

Jup. Strange; what's going on there…

@graaff
Copy link
Author

graaff commented Sep 21, 2011

If the conclusion is that jruby 1.5 is broken then that is fine with me, but unfortunately we're still stuck with that version of jruby on Gentoo which means I'll have to wait to add coderay 1.0.0 to Gentoo until that is resolved.

@korny
Copy link
Member

korny commented Sep 22, 2011

I see. Even if it's an incompatibility issue on 1.5.4, I'd like to make it work for you.

  • The first Failure is not problematic, since it's just an expected warning missing.
  • The second one might also not be a problem if you don't use plugins except for the ones in the distribution.

So I'd say, try to upgrade — even with the failing tests (for now).

@graaff
Copy link
Author

graaff commented Sep 26, 2011

We offer our users the option to run tests as part of the installation procedure of a package (for ruby as well as other packages that offer tests), so I can't just update the package without addressing this in a more structured way, either by removing the specific failing tests or depending on jruby 1.6 once that is added to Gentoo. Bit strapped for time now but I'll keep in mind that I can drop those tests if needed.

@korny
Copy link
Member

korny commented Sep 26, 2011

Commit ec60c83 fixes the first issue; the test was broken here, not the library.

The second issue is caused by a JRuby bug that has been fixed in 1.6: http://jira.codehaus.org/browse/JRUBY-4885?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

@graaff
Copy link
Author

graaff commented Sep 27, 2011

Thanks for looking in to this. For Gentoo I've commented out both tests for now, until we can depend on jruby 1.6. I guess this can be closed?

@korny
Copy link
Member

korny commented Sep 27, 2011

Okay.

@korny korny closed this as completed Sep 27, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants