-
Notifications
You must be signed in to change notification settings - Fork 827
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
"the object has been modified" errors seen during allocation #3553
Comments
More and more! This is killing me. |
This is the same conflict @gongmax sees in perf tests, and I assume it's because two allocators try to allocate the same GameServer but fail (and it's somehow not retried by the allocator). |
This is also mentioned in the load test README: agones/test/load/allocation/README.md Lines 62 to 64 in c1320ee
|
…allocation count to 98 The allocator is generating conflicts: see #3553
The actual bug is here: https://github.com/googleforgames/agones/blob/2023077aff4125b9d9822c5d20cd773d13138385/test/e2e/gameserverallocation_test.go#L1423 When we tried to accept errors in googleforgames#3750, we forgot to change this t.Errorf to a simple log. Along the way, some cleanup. Towards googleforgames#3553
The actual bug is here: https://github.com/googleforgames/agones/blob/2023077aff4125b9d9822c5d20cd773d13138385/test/e2e/gameserverallocation_test.go#L1423 When we tried to accept errors in googleforgames#3750, we forgot to change this t.Errorf to a simple log. Along the way: * change the timing of the scale-down so it happens more probably in the middle of the allocations, which was the intent. By my guess, 3s might be past all allocations. Also add a log to see if I'm right. * minor cleanup Towards googleforgames#3553
The actual bug is here: https://github.com/googleforgames/agones/blob/2023077aff4125b9d9822c5d20cd773d13138385/test/e2e/gameserverallocation_test.go#L1423 When we tried to accept errors in googleforgames#3750, we forgot to change this t.Errorf to a simple log. Along the way: * change the timing of the scale-down so it happens more probably in the middle of the allocations, which was the intent. By my guess, 3s might be past all allocations. Also add a log to see if I'm right. * minor cleanup Towards googleforgames#3553
…ake (#3831) The actual bug is here: https://github.com/googleforgames/agones/blob/2023077aff4125b9d9822c5d20cd773d13138385/test/e2e/gameserverallocation_test.go#L1423 When we tried to accept errors in #3750, we forgot to change this t.Errorf to a simple log. Along the way: * change the timing of the scale-down so it happens more probably in the middle of the allocations, which was the intent. By my guess, 3s might be past all allocations. Also add a log to see if I'm right. * minor cleanup Towards #3553
'This issue is marked as Stale due to inactivity for more than 30 days. To avoid being marked as 'stale' please add 'awaiting-maintainer' label or add a comment. Thank you for your contributions ' |
What happened:
The failed e2e test: TestGameServerAllocationDuringMultipleAllocationClients
What you expected to happen:
Pass all the time
How to reproduce it (as minimally and precisely as possible):
It fails sometimes in the CI
Anything else we need to know?:
Environment:
kubectl version
): 1.28The text was updated successfully, but these errors were encountered: