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
My team has been hitting this problem with a larger test environment where one client will be querying VMs to get their properties and another client will be making requests to customize and power on VMs.
When we run tests for this with -race option, it occasionally fails mentioning a data race with one thread in the customize function of PowerOn and another thread serializing an object (I'm guessing the VM).
To Reproduce
Steps to reproduce the behavior:
I added the following test to govmomi/simulator/virtual_machine_test.go
Expected behavior
I either expect locks to prevent the data race as it appears to be server-side (simulator) code, so a client against non-simulator wouldn't be expected to serialize their calls.
Describe the bug
My team has been hitting this problem with a larger test environment where one client will be querying VMs to get their properties and another client will be making requests to customize and power on VMs.
When we run tests for this with
-race
option, it occasionally fails mentioning a data race with one thread in the customize function of PowerOn and another thread serializing an object (I'm guessing the VM).To Reproduce
Steps to reproduce the behavior:
go test -v -count=1 --race -run TestVmCustomizeStress github.com/vmware/govmomi/simulator
.Expected behavior
I either expect locks to prevent the data race as it appears to be server-side (simulator) code, so a client against non-simulator wouldn't be expected to serialize their calls.
Affected version
Using commit 7be4a88.
Additional context
Sorry if this seems like a contrived case, but I tried to simplify a product use-case to something I can copy/paste.
The text was updated successfully, but these errors were encountered: