You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Michael Allen (JIRA)" <ji...@apache.org> on 2014/03/25 18:50:16 UTC

[jira] [Commented] (ACCUMULO-2549) ShellTest sometimes fails because of order of authentication strings returned

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

Michael Allen commented on ACCUMULO-2549:
-----------------------------------------

There was some local speculation that the version of the JDK may play a role in the order in which that string of authorizations is constructed, but I personally didn't try and test that theory.

> 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
>
>         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)