You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As i found we have a TestAuthJWTExpire that tests the expire conditions, so i think we are good to increase the TTL to something larger, Also we had the same issue here too #16523 that got fixed with increasing the ttl. I'm testing it to see affects on other tests meanwhile i thought sharing this and ask for your'e opinion would be a good idea too.
Which Github Action / Prow Jobs are flaking?
E2E / test (linux-386-e2e) (pull_request)
https://github.com/etcd-io/etcd/actions/runs/8199906821/job/22425749141?pr=17555
Which tests are flaking?
TestCtlV3AuthAndWatchJWT
Github Action / Prow Job link
https://github.com/etcd-io/etcd/actions/runs/8199906821/job/22425749141?pr=17555
Reason for failure (if possible)
jwt token is expired after the 1s TTL.
2024-03-08T07:05:13.928
test started to launch etcd process but this step is aftere2e.NewConfigJWT()
.So it is expected that after more than 1s that the token is expired and watch is cancelled by server.
Log snippets from the above github action failed test.
Anything else we need to know?
Please update the test to use longer TTL... I am not sure whether other tests are also impacted by this race condition.
https://github.com/etcd-io/etcd/blob/main/tests/e2e/ctl_v3_auth_test.go#L33
The text was updated successfully, but these errors were encountered: