[
https://issues.apache.org/jira/browse/YETUS-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759643#comment-16759643
]
Allen Wittenauer commented on YETUS-782:
----------------------------------------
Upon further investigation, it would appear that it is unhappy with some of the
.erb files in the Yetus source tree.
> rubylint is broken
> ------------------
>
> Key: YETUS-782
> URL: https://issues.apache.org/jira/browse/YETUS-782
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Affects Versions: 0.9.0
> Reporter: Allen Wittenauer
> Priority: Major
> Fix For: 0.10.0
>
>
> Given the errors showing up on the console, I'm pretty convinced ruby lint is
> broken. We should investigate:
> {code}
> /var/lib/gems/2.3.0/gems/slop-3.6.0/lib/slop.rb:505:in `process_item':
> presenter expects an argument (Slop::MissingArgumentError)
> from /var/lib/gems/2.3.0/gems/slop-3.6.0/lib/slop.rb:241:in `block in
> parse!'
> from /var/lib/gems/2.3.0/gems/slop-3.6.0/lib/slop.rb:238:in `each'
> from /var/lib/gems/2.3.0/gems/slop-3.6.0/lib/slop.rb:238:in
> `each_with_index'
> from /var/lib/gems/2.3.0/gems/slop-3.6.0/lib/slop.rb:238:in `parse!'
> from /var/lib/gems/2.3.0/gems/slop-3.6.0/lib/slop.rb:211:in `parse'
> from /var/lib/gems/2.3.0/gems/ruby-lint-2.3.1/bin/ruby-lint:95:in `<top
> (required)>'
> from /usr/local/bin/ruby-lint:23:in `load'
> from /usr/local/bin/ruby-lint:23:in `<main>'
> {code}
> It likely also means that rubylint's exit status isn't being checked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
