-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Flaky test: org.keycloak.testsuite.federation.sync.SyncFederationTest#test03ConcurrentSync #17430
Comments
Happened here as well: #17419 |
org.keycloak.testsuite.federation.sync.SyncFederationTest#test03ConcurrentSyncKeycloak CI - Base IT (5) / Pull Request #17429
|
org.keycloak.testsuite.federation.sync.SyncFederationTest#test03ConcurrentSyncKeycloak CI - Base IT (5) / Pull Request #17490
|
Managed to reproduce this locally using Here's a more detailed trace:
|
org.keycloak.testsuite.federation.sync.SyncFederationTest#test03ConcurrentSyncKeycloak CI - Base IT (5) / Pull Request #19058
|
I cannot make it fail in my env, even using one cpu only. But my feeling is that the provider cannot be removed because the other transaction in the sync is still doing things. For example:
So I'm going to modify a bit the test, and the exception in the delete will be swallowed. The next test is going to use another provider name to avoid issues if it cannot be removed. |
org.keycloak.testsuite.federation.sync.SyncFederationTest#test03ConcurrentSyncKeycloak CI - Base IT (5) / Pull Request #19098
|
2 similar comments
org.keycloak.testsuite.federation.sync.SyncFederationTest#test03ConcurrentSyncKeycloak CI - Base IT (5) / Pull Request #19098
|
org.keycloak.testsuite.federation.sync.SyncFederationTest#test03ConcurrentSyncKeycloak CI - Base IT (5) / Pull Request #19098
|
org.keycloak.testsuite.federation.sync.SyncFederationTest#test03ConcurrentSync
Keycloak CI - Base IT (5) / Pull Request #17378
The text was updated successfully, but these errors were encountered: