Fix data race in unit tests #318
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#318
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-node:fix/processors_race"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #311
basically it is not a
node
butir
?@ -255,3 +255,3 @@
proc.handleBind(evBind)
time.Sleep(time.Second)
for proc.pool.Running() > 0 {
How about
require.Eventually
? -- we can set maximum wait time there.A data race occurred due to a read before the pool goroutine was completed. I think it will end up being the same data race in case of
eventually
.Why, though?
Eventually
will fail the test if the condition is not true after some time, so the following code will not be executed.610f1f39d1
to554ac18c91
fixed
554ac18c91
tof4e522da68
f4e522da68
to2f6757c828