accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2549) ShellTest sometimes fails because of order of authentication strings returned
Date Fri, 13 Jun 2014 18:51:02 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030992#comment-14030992
] 

ASF subversion and git services commented on ACCUMULO-2549:
-----------------------------------------------------------

Commit e6171e6b2a293ac5561e20147e005df2d0e6c06a in accumulo's branch refs/heads/master from
[~mallen]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=e6171e6 ]

ACCUMULO-2549 Fixes ShellTest

Authorizations were coming back from getauths in an unexpected
order.  This patch changes the test to expect not a specific
string a but a list of expected authorization entries.

Signed-off-by: Mike Drob <mdrob@cloudera.com>


> ShellTest sometimes fails because of order of authentication strings returned
> -----------------------------------------------------------------------------
>
>                 Key: ACCUMULO-2549
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2549
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.5.1
>            Reporter: Michael Allen
>            Priority: Minor
>             Fix For: 1.5.2, 1.6.1, 1.7.0
>
>         Attachments: ACCUMULO-2549-Fixes-ShellTest.patch
>
>
> {{org.apache.accumulo.core.util.shell.ShellTest}} sometimes fails for me when run from
the Maven command line.  Tracing down, I see that line 154 (1.5.1 version) contains the following
> {noformat}
>     exec("getauths", true, "y,z,x");
> {noformat}
> This test expects that the set of authorizations returns from the {{getauths}} command
always come in the particular order "y,z,x".  For whatever reason, on my machine, they came
out in a different order ("x,y,z" for the record).
> My proposed fix (patch shortly) would be to have the test look for those individual label
strings returned within the authorization string.  I think this is a more accurate and future
proof test than what's in there now.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message