You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Larry McCay (Jira)" <ji...@apache.org> on 2024/10/11 16:35:00 UTC

[jira] [Updated] (KNOX-3069) Flakey Test - TokenServiceResourceTest

     [ https://issues.apache.org/jira/browse/KNOX-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Larry McCay updated KNOX-3069:
------------------------------
    Summary: Flakey Test - TokenServiceResourceTest  (was: Flaky Test - TokenServiceResourceTest)

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