-
Notifications
You must be signed in to change notification settings - Fork 24.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CI] TokenServiceTests testTokenExpiry fails #30062
Comments
Adjusts the maximum fast forward time for token expiration tests to be 5 seconds before actual token expiration so that the test won't fail even when upperlimit is randomly selected. Resolves: elastic#30062
Adjust fast forward for token expiration test Adjusts the maximum fast forward time for token expiration tests to be 5 seconds before actual token expiration so that the test won't fail even when upperlimit is randomly selected. Resolves: #30062
Adjust fast forward for token expiration test Adjusts the maximum fast forward time for token expiration tests to be 5 seconds before actual token expiration so that the test won't fail even when upperlimit is randomly selected. Resolves: elastic#30062
Despite #30668 a failure of the same test with an identical stack trace occurred in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+matrix-java-periodic/ES_BUILD_JAVA=java11,ES_RUNTIME_JAVA=java11,nodes=virtual&&linux/65/console:
This didn't reproduce using:
|
#30668 was sadly never backported to 6.x, my bad. I will fix this now |
Adjust fast forward for token expiration test Adjusts the maximum fast forward time for token expiration tests to be 5 seconds before actual token expiration so that the test won't fail even when upperlimit is randomly selected. Resolves: #30062
Thanks @jkakavas, I assumed the fix was in 6.x because that PR was labelled with 6.3.0 and 6.4.0. I've changed the labels on the PR to show the earliest version it's in is now 6.6.0. |
Original comment by @cbuescher:
LINK REDACTED
Can reproduce locally with:
Failure:
The text was updated successfully, but these errors were encountered: