[
https://issues.apache.org/jira/browse/KNOX-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891310#comment-17891310
]
ASF subversion and git services commented on KNOX-3069:
-------------------------------------------------------
Commit 89b7139dc314087287266a976c1dd20accb6f776 in knox's branch
refs/heads/dependabot/maven/org.apache.derby-derby-10.17.1.0 from Larry McCay
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=89b7139dc ]
Knox 3069 (#939)
* KNOX-3069 - add a sleep to ensure uniqueness
> Flakey Test - TokenServiceResourceTest
> --------------------------------------
>
> Key: KNOX-3069
> URL: https://issues.apache.org/jira/browse/KNOX-3069
> Project: Apache Knox
> Issue Type: Bug
> Components: JWT
> Reporter: Larry McCay
> Priority: Minor
> Fix For: 2.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> TokenServiceResourceTest - testLimitingTokensPerUser method acquires many
> tokens within a tight for loop and does not insure that the tokenIds are
> unique.
> This results in test failures for the unlimited tokens per user on certain
> machines.
> This may also point to a larger concurrency problem which needs
> investigation. Will file a separate JIRA for this. This may be an issue with
> the test or the UUID use for the tokenID in general. In the meantime, we
> can't have builds failing on certain machines.
> This change interrogates the response and adds an assertion to ensure that
> the tokenId is unique. It seems the time spent in doing the check "fixes" the
> failures. The same "fix" was accomplished with a sleep of 1ms between token
> acquisitions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
