Expired lock test fails occasionaly

[roman-khimov]

Expected Behavior

Green.

Current Behavior

https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/2136-1732220712/index.html#suites/295ed2e000f8fa6f3ade59cc13b98615/6deb00ef86b7dc66/
https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/2136-1732221029/index.html#suites/295ed2e000f8fa6f3ade59cc13b98615/c49306c8063b4d85/

It fails at the waiting stage, all iterations returns the object.

Possible Solution

Needs to be investigated, either it's a test issue (not giving enough time for things to settle) or it's a bug. From the first glance it looks as a bug.

Steps to Reproduce (for bugs)

Run tests.object.test_object_lock.TestObjectLockWithGrpc#test_expired_object_should_be_deleted_after_locks_are_expired

Your Environment

• Version used: any recent master
• Server setup and configuration:
• Operating System and version (uname -a):

[roman-khimov]

https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/756-1734907387/index.html#suites/295ed2e000f8fa6f3ade59cc13b98615/54ab2cfa34853769/