engine: fix TestEvacuateShard

It looks like on a slow (few-core?) machine put operation can be failed because the internal pool has not been freed from the previous iteration (another shard is tried then and additional "fake" relocation is detected in the test). Closes #2860. Signed-off-by: Pavel Karpy <[email protected]>
nspcc-dev · Jun 12, 2024 · 161489b · 161489b
1 parent 5d9e36d
commit 161489b
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/pkg/local_object_storage/engine/evacuate_test.go b/pkg/local_object_storage/engine/evacuate_test.go
@@ -28,7 +28,7 @@ func newEngineEvacuate(t *testing.T, shardNum int, objPerShard int) (*StorageEng
 
 	e := New(
 		WithLogger(zaptest.NewLogger(t)),
-		WithShardPoolSize(1))
+		WithShardPoolSize(uint32(objPerShard)))
 
 	ids := make([]*shard.ID, shardNum)