Am 20/07/2022 um 15:06 schrieb Vladimir Sementsov-Ogievskiy:
> On 7/19/22 15:00, Emanuele Giuseppe Esposito wrote:
>>
>>
>> Am 11/07/2022 um 15:08 schrieb Vladimir Sementsov-Ogievskiy:
>>>
>>> That made me ask:
>>>
>>> 1. Are all tests always run in main loop? If yes, why to protect status
>>>
On 7/19/22 15:00, Emanuele Giuseppe Esposito wrote:
Am 11/07/2022 um 15:08 schrieb Vladimir Sementsov-Ogievskiy:
That made me ask:
1. Are all tests always run in main loop? If yes, why to protect status
reading in test_complete_in_standby() ?
2. Maybe, we don't need to protect anything
Am 11/07/2022 um 15:08 schrieb Vladimir Sementsov-Ogievskiy:
>
> That made me ask:
>
> 1. Are all tests always run in main loop? If yes, why to protect status
> reading in test_complete_in_standby() ?
>
> 2. Maybe, we don't need to protect anything here? Why to protect other
> things if we
On 7/6/22 23:15, Emanuele Giuseppe Esposito wrote:
Add missing job synchronization in the unit tests, with
explicit locks.
We are deliberately using _locked functions wrapped by a guard
instead of a normal call because the normal call will be removed
in future, as the only usage is limited to
Add missing job synchronization in the unit tests, with
explicit locks.
We are deliberately using _locked functions wrapped by a guard
instead of a normal call because the normal call will be removed
in future, as the only usage is limited to the tests.
In other words, if a function like
